Testers needed: flat development (4.7+ only)

Summer · 2020-02-04 08:14:01

colak wrote #321498:

is the plugin needed? Flat files are now supported in the core.

em… I feel like I missed something…

Bloke · 2020-02-04 09:01:46

colak wrote #321498:

is the plugin needed? Flat files are now supported in the core.

Yes, but they’re not supported direct from disk during development. This plugin adds that.

etc · 2020-02-04 11:23:35

What a n00b I am! Thanks Summer.

Bloke · 2020-08-17 08:31:18

I may be using this on a project soon that’s managing their Txp templates on disk for git control. What is the status of the plugin with the dev/live workflow?

From my understanding the plugin does not inject any data into the database, rather just lets the database fetch assets from disk while in testing/debug mode, correct? So does it honour the dev assets that are set, for anyone using developer preview? What happens for those not using developer preview? And how does it work if you have a mix of dev/live assets being served from the DB?

Secondly, I guess after development is done and all signed off, this is the process:

Switch production mode to Live.
From the Themes panel, select theme and Import from disk.
From the Sections panel, select sections and Deploy to live, as normal.

Correct?

etc · 2020-08-17 09:18:53

IIRC, etc_flat fetches assets from themes folder. It is important to notice that there is no live/dev versions of a theme, the entire theme can be live or dev individually for each section. So, everything happens (almost) exactly as usual: logged-in users will get their dev assets served from disk, and other visitors will be served live assets, but from db.

The plugin does not keep db/disk in sync, leaving it with admins.

Bloke · 2020-08-17 09:22:51

Of course, that makes perfect sense. Thanks for the clarification.

etc · 2020-08-17 10:54:34

Also, styles are not handled by this plugin (there is no ‘fetch css’ callback), but one can link to their flat versions in core anyway.

mrdale · 2020-10-09 18:03:31

My usage of textpattern and contribution to this forum has dropped off significantly in the last couple of years due to vocational changes. I had a really good workflow going using the last version of oui_flat.

Custom form types via subdirectories helped me keep a super clean codebase
Automatic import, allowed me to have a super efficient headless CMS for dev tasks

could these features be enabled?

From scanning this topic I can see that most people don’t groove on the idea of automatic import, but it could be added as a admin pref or even a hidden pref.

philwareham · 2020-10-09 18:49:44

Hi Dale, good to hear from you. You can enable additional subdirectories for forms in the advanced options section of prefs (first turn on advanced options at bottom of admin prefs section). In the custom form templates field add subdirectories as follows:

[shortcodes]
*="Shortcodes"
[another-directory-name]
*="Another form type name"

As for auto import, I think there was a plugin to allow that when site is set to debug, or something like that.

mrdale · 2020-10-09 18:57:42

philwareham wrote #326289:

As for auto import, I think there was a plugin to allow that when site is set to debug, or something like that.

Anyone know of this mystery plugin? :)

etc · 2020-10-09 19:44:07

mrdale wrote #326290:

Anyone know of this mystery plugin? :)

When logged in in debug/testing modes (and etc_flat enabled), you get assets directly from the disk. Once happy with the result, import them into your theme and serve your visitors?

mrdale · 2020-10-09 23:03:20

etc wrote #326295:

When logged in in debug/testing modes (and etc_flat enabled), you get assets directly from the disk.

I must be doing something wrong.

enable etc_flat
testing mode
delete a couple of forms in the file system
alter a couple of pages and forms in the filesystem
visit the forms and see a message
visit the pages and see a message

Result: No forms deleted, no pages altered.
Desired workflow: I merrily alter my codebase in the file system and anytime the site is hit from anywhere my edits are imported into the database.

I like this workflow because I generally work on a staging server and can develop quicker when I don’t have to page around in a UI. I periodically push up a new version to the server and/or github

Anyone else feel like that would be a good workflow. Anyone else game?

Textpattern CMS

Textpattern CMS support forum

#169 2020-02-04 08:14:01

Re: Testers needed: flat development (4.7+ only)

colak wrote #321498:

#170 2020-02-04 09:01:46

Re: Testers needed: flat development (4.7+ only)

colak wrote #321498:

#171 2020-02-04 11:23:35

Re: Testers needed: flat development (4.7+ only)

#172 2020-08-17 08:31:18

Re: Testers needed: flat development (4.7+ only)

#173 2020-08-17 09:18:53

Re: Testers needed: flat development (4.7+ only)

#174 2020-08-17 09:22:51

Re: Testers needed: flat development (4.7+ only)

#175 2020-08-17 10:54:34

Re: Testers needed: flat development (4.7+ only)

#176 2020-10-09 18:03:31

Re: Testers needed: flat development (4.7+ only)

#177 2020-10-09 18:49:44

Re: Testers needed: flat development (4.7+ only)

#178 2020-10-09 18:57:42

Re: Testers needed: flat development (4.7+ only)

philwareham wrote #326289:

#179 2020-10-09 19:44:07

Re: Testers needed: flat development (4.7+ only)

mrdale wrote #326290:

#180 2020-10-09 23:03:20

Re: Testers needed: flat development (4.7+ only)

etc wrote #326295:

Board footer