Could we feasibly see unlimited CFs in 2017? :)

Destry · 2017-02-08 11:01:24

It’s the single biggest development in the history of Txp. I can hardly wait for it. It basically makes Txp a fully componentized system.

Are there any secret drawings on papyrus available that depict new Write panel design/layout concepts in relation? Because I would expect some reimagining there. / Phil’s eyes roll /

I came across this discussion for a new <h> tag, and was looking at some of the benefits and challenges that may entail. But what struck me is how unlimited CFs will make dealing with things like this so much easier. No longer struggling with the ‘body blob’, as they call it in content strategy circles.

In a new site I’m working on for myself, I’ve begun using more section regions to break up longform content, and it will be nice to treat those regions as their own CF textareas and piece them together. That will mimic how I draft them in iA Writer and Ulysses too, different page for each section/chapter.

But that just scratches the surface from what I can see.

colak · 2017-02-08 14:56:57

Destry wrote #303889:

It’s the single biggest development in the history of Txp. I can hardly wait for it. It basically makes Txp a fully componentized system.

+1

bici · 2017-02-09 01:21:23

does CF = Custom Fields?

if so i’m on board.

jakob · 2017-02-09 11:08:54

Without meaning to add any stress to the good work of the devs, I just wanted to echo my interest in this. glz_custom_fields is a standard installation in all but the simplest of my sites.

GugUser · 2017-02-09 13:17:22

jakob wrote #303912:

Without meaning to add any stress to the good work of the devs, I just wanted to echo my interest in this. It’s a standard installation of all but the simplest of sites.

Luckily glz_custom_fields still works. I use it on all my sites. But I agree, a complete integration in the core would be better.

milosevic · 2017-02-09 17:50:05

+1

jpdupont · 2017-02-09 20:07:48

+1

Related ? : a mck_snippets like in the core :-)

phiw13 · 2017-02-10 02:59:37

GugUser wrote #303914:

Luckily glz_custom_fields still works.

Does it? Well sort of, depending on what type of custom fields you create. I get quite a few problems.

GugUser · 2017-02-10 04:22:15

phiw13 wrote #303931:

Does it?

So far I haven’t had such experiences, but now I’m startled…

hidalgo · 2017-02-10 04:40:32

GugUser wrote #303932:

So far I haven’t had such experiences, but now I’m startled…

I think some of these problems appear on newer versions of PHP, I tried moving a site onto PHP 7 with glz_custom_fields and it was a no go.

So yes, core unlimited custom files would be amazing.

GugUser · 2017-02-10 05:01:09

Strange, I’m on PHP 7.0.2 without any glz_custom_fields problems. Oh, fright, I thought everything was fine.

phiw13 · 2017-02-10 05:05:23

GugUser wrote #303932:

So far I haven’t had such experiences, but now I’m startled…

To be fair, the big issue is with textarea, other type of fields (text field, radio, checkbox) seem to work OK, albeit with a bit of noise in testing / debugging mode. I did not test the calendar widgets. And the plugin would need some styling love… And I am not sure how well this all works with the more recent versions of PHP / MySQL.

But yes, Custom fields is something that needs some serious attention. There is a custom fields branch on Github, where Stef had parked some (preliminary) work.

Textpattern CMS

Textpattern CMS support forum

#1 2017-02-08 11:01:24