Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Situation report for Textpattern 4.6 and beyond
simoin wrote #278691:
…especially seeing as TXP Magazine, (which is sorely missed) is dormant at the moment.
Rest assured dormant is all it is at the moment. Though to be honest, it’s alive right now. Problem is there are no article contributions, and the editor has a dozen other more important things to do than chase people down and charm them into producing something. The editor could do all the journalism himself, but then it would make sense to rename the magazine Destry’s TXP Blog, and there’d be no fun in that. ;)
I do have a question in spirit of the thread, however, devs… Will there be a Markdown filter in 4.6? (Pretty please.)
Offline
Offline
Re: Situation report for Textpattern 4.6 and beyond
Isn’t there there’s already Markdown filter support in 4.6?
Edit: beat me to it!
Last edited by philwareham (2014-02-13 15:07:41)
Offline
Re: Situation report for Textpattern 4.6 and beyond
Bloke wrote #278776:
…I might put some effort into writing a migration plugin for glz_custom_fields (the core will only cater for its own fields: varchar)
Was just coming here to ask about that. I haven’t really relied on glz_CFs before, but I’m currently in a position that needs thinking about it for the simple reason of field types (principally textarea) other than text boxes. I could just sit with using core for now if that would make for lower-overhead upgrade come 4.6. In fact, I’d rather do that if it made for easier upgrade and made your life easier too.
…and finally extend the fields out to images, files and links.
Why not? ;)
Maybe users too, which might remove the necessity for smd_bio.
Makes sense… But then do you bring user_manager functionality too?
For clarification, I doubt all this will be in the first drop. I’d like to get articles done for 4.6.0 and then roll support for the remaining content types out in subsequent releases.
I think anything more would put people into shock. Better take this new dope in stages.
Offline
Re: Situation report for Textpattern 4.6 and beyond
@wet and phil, Thanks.
Offline
Re: Situation report for Textpattern 4.6 and beyond
Praying to the golden vache that forces align on Bloke’s effort with native custom field extension in Articles for 4.6. For me, it’s the single-most anticipated new feature and (along with the Markdown filter) worthy of a 4.6 launch alone. So, yeah, Phil, be sure to take it into account in the UI. ;)
Offline
Re: Situation report for Textpattern 4.6 and beyond
Bloke, Other Devs – just a quick question regarding custom fields.
I know in the past you have been awesome in making TXP upgrades backwards compatible with certain plugins and so on. So I was wondering what will happen to sites using Gerhards custom fields when custom fields are brought into the core?
Will they still work standalone as they are? Will they be some merge during the upgrade?
Just asking as I got an upgrade to do on a txp site which is going to use a lot of custom fields.
Thanks
Offline
Re: Situation report for Textpattern 4.6 and beyond
tye wrote #279447:
what will happen to sites using Gerhards custom fields when custom fields are brought into the core?
Core won’t pander to plugins, regardless of how awesome they are, because that’s a hiding to nowhere. Think about the different versions of glz_cf, for example. Trying to migrate data might well cause core upgrade problems, which we can’t risk.
The best I can offer — subject to this damn thing working at all(!) — will be a glz_cf migration script that pulls custom field definitions > 10 into the new CF table, and imports the data as best as it can into the core tables that hold CF values.
It’ll be up to you to delete the original custom_N fields from the textpattern table, mostly as a fallback in case something during migration goes wrong so you can copy the data out manually without losing anything.
Oh, and regarding whether glz_cf will work on a 4.6 install, the answer is “maybe”. At present I’ve hacked the existing functions during testing, which means they’re most certainly NOT backwards compatible. But if it works, I’ll probably migrate the code to a PSR-0 style structure and revert the existing functions to their current functionality which means glz_cf would continue to work alongside core CFs. Lots of unknowns at present, so nothing is concrete.
Last edited by Bloke (2014-03-04 22:33:42)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Situation report for Textpattern 4.6 and beyond
That’s the right approach I think. I’d rather the custom fields were the best implementation they possibly could be, and not hindered by having to support legacy plugin code.
Offline
Re: Situation report for Textpattern 4.6 and beyond
Thanks for the transparency – answers a few questions – it was just something I needed to be aware of :)
Offline
Re: Situation report for Textpattern 4.6 and beyond
philwareham wrote #279450:
That’s the right approach I think. I’d rather the custom fields were the best implementation they possibly could be, and not hindered by having to support legacy plugin code.
+1
one way is to list what will not be supported. then folks have the choice of not upgrading until they get their stuff in order.
4.6 is a clean break. “don’t upgrade until you have determined what will not be supported. Questions? Contact the plugin author “
…. texted postive
Offline
Re: Situation report for Textpattern 4.6 and beyond
Bloke wrote #279448:
subject to this damn thing working at all(!)
Say it ain’t so, Bloke. Say it ain’t so! Get the whole damn squad working on it if you have to.
(And, right. Old plugins should be adapting to core, not the other way around. Time to move forward.)
Offline