Textpattern CMS

#1 2012-02-26 07:26:28

wet

Developer Emeritus

From: Schoerfling, Austria

Registered: 2005-06-06

Posts: 3,323

Website Mastodon

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.

#2 2012-02-26 07:31:37

wet

Developer Emeritus

From: Schoerfling, Austria

Registered: 2005-06-06

Posts: 3,323

Website Mastodon

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.php

#3 2012-02-26 13:34:03

ruud

Developer Emeritus

From: a galaxy far far away

Registered: 2006-06-04

Posts: 5,068

Website

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.

#4 2012-02-26 16:43:11

Gocom

Developer Emeritus

From: Helsinki, Finland

Registered: 2006-07-14

Posts: 4,533

Website

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.

---

Rah | GitHub