Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Textpattern's ongoing development
jakob wrote #342221:
[…] so there is, as yet, no conversion for glz_cf or any of my other content-type custom field plugins. I don’t think the devs have tackled that either. […]
Yes, I know that, and I did not expect those glz_CF to work at all. I just pointed out that as far as my content is concerned, nearly everything got ported over as correctly. It actually surprised me a little that jcr_images_custom works (possibly because it is a more recent / modern code and only of the type text).
Anyway, things work surprisingly well so far, compare to a few months back.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: Textpattern's ongoing development
phiw13 wrote #342220:
I was pleasantly surprised that my local test site… happily upgraded to 5.0.0-dev.
Yay. I’m pleased that worked… mostly. Even though 5.0 is going to be a big departure, there’s no point completely shutting out people’s existing sites from an upgrade viewpoint, so we will take as many steps as possible to assist migration.
It lost all its article custom fields (glz_cf).
The plan, as Jools says, is to have it seamlessly migrate text-based fields natively, whether they’re part of the 10 core or the glz_cf extensions. However, those of other types like select lists, date pickers and checkbox sets won’t be migrated by core directly.
Instead, when the new DB structure and way of working stabilises more, one of us will write a conversion utility to migrate these “other” types to Txp 5.0.0 parlance. This will need to be run prior to upgrading. But the challenge here is that the new DB structure won’t be available at that point of the upgrade process.
So, my initial thinking is that this tool will simply prepare a “backup” of your CF data and definitions into an .xml file or two (most likely, or possibly JSON).
With the file(s) in place in your installation, when you upgrade, the end of the _to_5.0.0.php script will check for their existence and run our standard ImportXML() on them, thus recreating all the non-varchar field data and options. Transmit users will need to ensure they don’t accidentally blat the XML file(s) if they do transfer new files that way (I believe its default operation is still Replace not Merge).
I did a quick rebuild (recreation) of a couple of the CFs I had and the output worked as expected on the front-end.
That’s brilliant to know, thanks for checking. I haven’t been able to reliably test recent changes on my live server because I’ve had so many partial pushes to it that it seems to be corrupted. Tags don’t seem to output anything (or nothing gets stored via the back-end: I haven’t debugged which).
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