Textpattern CMS support forum
Textpattern as a modular system
My reflections on global topics… ;-)
I suggest gradually moving to the modular Textpattern structure. It would be very convenient in the admin interface with one click to enable/disable modules. Create/Drop(if table is empty) related SQL tables, include/or not module tags and module admin interface.At the first stage, can start with the modules:
/vendors/loader. Move some code from
/include/txp_* (admin interface)to
- SQL table structure for create/drop tables (Soon will be). Move too
- Need to do: module.prefs Place too
Yes, this is a hard and thankless job, but in the future it will help us to get a flexible and powerful system. For example, can have several alternative modules for comments/images (switching them from the admin interface). The most successful and time-tested plugins can be included in the basic system as modules.For example:
smd_tags(and/or) some variant Unlimited Category (I would like to leave the possibility to use category1 and category2, since queries to them are carried out as quickly as possible)
rah_external_output– here can still expand the possibilities (maybe interface for public ajax)
gbp_permanent_links– here is a topic for a separate conversation. I would suggest introducing the concept of an alternative handler
preText(). For maximum compatibility, leave the original
preText(). If compatibility with old permlinks is not needed, then let’s use another permlink building. It would be nice to add support for subdomains.
I’m not completely versed in this issue, but perhaps the concept of modules is suitable for Unlimited Custom Fields.