Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
Plugin caching
In another thread, Gocom wrote:
—
wet wrote:
keeping plugin all metadata in the database and just cache the code in the file system. Suggestions (or even patches, gasp!) are welcome.
That might be the best option; gets rid of the forever running glob too. But it doesn’t necessarily make plugin management any easier. Which is why guys use it; to be able to install plugins via a single commit.
—
Thread split, follow-ups here.
Offline
Re: Plugin caching
We could mirror the metadata into a cache directory structure:
`-active
'
`-prio-0
'
`- abc_foo.php
`-prio-1
`-abc_bar.php
`-inactive
'
`-prio-0
'
`-xyz_omg.phpOffline
Re: Plugin caching
Or just write the code for active plugins into one big file, ordering the plugins within that file based in their priority. One file for the admin side, one file for the public side.
Offline
Re: Plugin caching
ruud wrote:
Or just write the code for active plugins into one big file, ordering the plugins within that file based in their priority. One file for the admin side, one file for the public side.
Loader files FTW. Now the next question is the format. Whether it’s just a PHP file which can be populated with anything, a simple flat file with just list of filenames, or a XML/INI (or similar) file that in addition also allows announcing flags (for preferences panel support).
One file for the admin side, one file for the public side.
One file for each type? Six files in total.
Offline
Pages: 1