Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: [RFC] Custom Fields: expirable?
etc wrote #340597:
The most cumbersome part is to adapt the language strings management.
That was horribly kludgy in my original implementation anyway. Keeping CF name changes in sync with lang keys and _instructions and so forth was not pretty.
It’d be nice to make things more atomic (start transaction)? That’d be a start. But if there’s a better way of managing them in a multilingual way, that’d be awesome.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: [RFC] Custom Fields: expirable?
Dunno, I have not really touched this part. Having some local immutable keys would be great. Calling them txpcf_1 would make custom fields export/import tricky, but some internal mapping table txpcf_name <-> meta_id might help.
Foreign keys would be helpful too, but MyISAM supports them poorly.
Offline