Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Testers needed: flat development (4.7+ only)
phiw13 wrote #313306:
Looks good from an organizational POV. But the strings…
- The
Stylespanel title should probably be something else (discussed upthread)- the
All stylestitle, shouldn’t that be something likestylesheets?
Thanks for testing, the strings are certainly subject to change. Probably something like this?
CSS (text/css)
JS (application/javascript)
...Offline
Re: Testers needed: flat development (4.7+ only)
etc wrote #313322:
Thanks for testing, the strings are certainly subject to change. Probably something like this?
CSS (text/css)...
That is already better, and has the advantage of being short (I was first thinking “stylesheets”, ”scripts”,… which is longer)
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
Offline
Re: Testers needed: flat development (4.7+ only)
I am wondering if there will eventually be a way to do without the rah_sitemap & rah_external plugins, through the assets tab.
At the moment and as far as I understand it, the assets tab can not parse any txp tags. Allowing such parsing might be of help. I realise that css is pointless to parse as we are talking about static files. Being able to parse other content though such as what rah_sitemap (xml) and rah_external (html) is doing is worth discussing.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
#100 2018-08-08 10:02:59
Re: Testers needed: flat development (4.7+ only)
colak wrote #313341:
At the moment and as far as I understand it, the assets tab can not parse any txp tags. Allowing such parsing might be of help. I realise that css is pointless to parse as we are talking about static files. Being able to parse other content though such as what rah_sitemap (xml) and rah_external (html) is doing is worth discussing.
You can enable assets parsing via Easter eggs code, setting $prefs['parse_css'] = true. It is not yet official because we have to find an optimal way to enable parsing: globally, by mimetype or even individually? Currently you can enable it globally, so every asset served via txp will be parsed. If you don’t need parsing some asset, serve it directly as flat file (after syncing with db), this will even be faster.
Open to discussion, as ever.
Offline
#101 2018-08-08 10:21:01
Re: Testers needed: flat development (4.7+ only)
etc – would it be helpful to fold Easter eggs and the associated flat themes testing files into the dev-demo site?
Offline
#102 2018-08-08 11:15:32
Re: Testers needed: flat development (4.7+ only)
gaekwad wrote #313343:
etc – would it be helpful to fold Easter eggs and the associated flat themes testing files into the dev-demo site?
Dunno, it would be funny, but you’d need to write a clear notice that this is not yet part of the “official” dev. And also manually sync with eventual updates. But if the demo site gets much feedback, it certainly would help.
Offline
#103 2018-08-08 16:00:32
Re: Testers needed: flat development (4.7+ only)
I’m running your Easter eggs plugin since 4.7 without any problems. I have also updated the plugin the other day when you re-posted it, but I am still working on some svg images to upload so as to check it. I will report back.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
#104 2018-08-08 16:04:21
Re: Testers needed: flat development (4.7+ only)
etc wrote #313342:
You can enable assets parsing via Easter eggs code, setting
$prefs['parse_css'] = true. It is not yet official because we have to find an optimal way to enable parsing: globally, by mimetype or even individually? Currently you can enable it globally, so every asset served via txp will be parsed. If you don’t need parsing some asset, serve it directly as flat file (after syncing with db), this will even be faster.Open to discussion, as ever.
I will check this tomorrow!!! Wonderful news. I actually do serve all assets as flat files generated by the easter eggs interface.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
#105 2018-08-08 16:48:58
Re: Testers needed: flat development (4.7+ only)
etc wrote #313342:
You can enable assets parsing via Easter eggs code, setting
$prefs['parse_css'] = true. It is not yet official because we have to find an optimal way to enable parsing: globally, by mimetype or even individually? Currently you can enable it globally, so every asset served via txp will be parsed. If you don’t need parsing some asset, serve it directly as flat file (after syncing with db), this will even be faster.Open to discussion, as ever.
Hi Oleg,
As this was easy I have tried it just now. The txp tags are not parsed… Unless of course I misunderstood your explanation where you wrote:
Currently you can enable it globally, so every asset served via txp will be parsed.
Does this mean under the Presentation>Styles tab or everywhere as in the forms, pages etc?
This is what I get
XML Parsing Error: prefix not bound to a namespace
Location: http://www.neme.org/themes/neme960/styles/sitemap.xml
Line Number 11, Column 1:<txp:article_custom section="events,participations,about,texts" exclude="1,2,44" break="" wraptag="url" limit="9999"><loc><txp:permlink /></loc><lastmod><txp:modified format="%Y-%m-%dT%H:%M:%SZ" /></lastmod></txp:article_custom>
^This is what I have in Presentation>Styles>sitemap.xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>http://www.neme.org/</loc></url>
<url><loc>http://www.neme.org/about/</loc></url>
<url><loc>http://www.neme.org/events/</loc></url>
<url><loc>http://www.neme.org/nac/</loc></url>
<url><loc>http://www.neme.org/participations/</loc></url>
<url><loc>http://www.neme.org/publications/</loc></url>
<url><loc>http://www.neme.org/related-links/</loc></url>
<url><loc>http://www.neme.org/texts/</loc></url>
<url><loc>http://www.neme.org/workshops/</loc></url>
<txp:article_custom section="events,participations,about,texts" exclude="1,2,44" break="" wraptag="url" limit="9999"><loc><txp:permlink /></loc><lastmod><txp:modified format="%Y-%m-%dT%H:%M:%SZ" /></lastmod></txp:article_custom>
</urlset>Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
#106 2018-08-08 17:02:33
Re: Testers needed: flat development (4.7+ only)
Oleg, I’ve not tried your new version yet, but did wan’t to report back on one thing when using etc_flat:
If you’re developed a site using etc_flat and working from the flat files, you can’t assign new page templates to sections without first upsyncing the theme files to the database. I guess that’s logical given that the panel is constructed using what’s in the txp_page table of the database. I presume the same will apply to the situations where you select a form from a drop-down, such as “override form” on the write panel.
It’s not a big deal but is different to how working with rah_flat/oui_flat used to work. If there’s no workaround, maybe it just needs noting in some future instructions.
TXP Builders – finely-crafted code, design and txp
Offline
#107 2018-08-08 19:57:17
Re: Testers needed: flat development (4.7+ only)
colak wrote #313353:
Hi Oleg,
Does this mean under the Presentation>Styles tab or everywhere as in the forms, pages etc?
This is what I get
XML Parsing Error: prefix not bound to a namespace...
Yiannis, have you edited the plugin code? It comes with $prefs['parse_css'] = false, you need to set the preference to true.
Offline
#108 2018-08-08 20:20:01
Re: Testers needed: flat development (4.7+ only)
jakob wrote #313355:
If you’re developed a site using etc_flat and working from the flat files, you can’t assign new page templates to sections without first upsyncing the theme files to the database. I guess that’s logical given that the panel is constructed using what’s in the txp_page table of the database. I presume the same will apply to the situations where you select a form from a drop-down, such as “override form” on the write panel.
It’s not a big deal but is different to how working with rah_flat/oui_flat used to work. If there’s no workaround, maybe it just needs noting in some future instructions.
Hi Julian, IIRC, rah|oui_flat have hooks that sync fs changes with db automatically (can’t imagine another way without too much code rewriting). That’s handy, but can be problematic if you develop a flat version (which you are the only one to see in 4.7, others are served from db) and make an error. If fs is synced with db then this error will be exposed to the whole world.
Offline