Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2006-06-26 02:32:48
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: [request] "Cascading" custom fields.
hakjoon wrote:
The long term plan for what I wanted to do was to try to implement something like MODX’s template variables (although not quite as powerful), but basically you would be able to control not only the name of Custom fields but also what field type it is so you could setup drop downs or checkboxes stuff like that.
That sounds powerful. Ok, I think I’ll just shelve my cascade idea for now as there hasn’t been a lot of interest expressed anyway :O)
— Steve
Offline
Re: [request] "Cascading" custom fields.
I’d just like to be a cheerleader on the sideline of this plugin conception :)
Offline
#15 2006-06-28 03:15:12
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: [request] "Cascading" custom fields.
Hello pieman,
regardless of the my following question, thanks for the cheerleading :O)
Can you clarify which ‘team’ you’re cheering for? Cascading fields or Hakjoon’s super-dooper per-section custom fields?
— Steve
Offline
Re: [request] "Cascading" custom fields.
can’t a man sit on the fence and cheer in peace these days?
;)
Well I kind of grasp the ‘cascade’ concept, but can’t really see the usefulness of specifying the contents of custom fields at a section/global level… couldn’t you can kind of do that already with <code><txp:if_custom_field name=“pies”><txp:custom_field name=“pies” /><txp:else />we’re all out of pies</txp:if_custom_field></code> in your form? Maybe I’m missing the point tho.. it happens!
My cheer was mainly for the idea of (DOM enabled or otherwise) reloading the custom fields visible in the Write tab when you assign it a Section.
I think it would make the user-interface a whole lot more friendly, and this would be another big step towards making Txp a stronger option for more complex sites.
Like Bloke, I use custom fields pretty extensivey and I know from experience that people have trouble remembering to use which fields in which sections. In my current build I’m naming them with the section name as a prefix, but that’s not really a great solution.
Ideally, I’d like there to be an extensions tab for custom fields, where you can assign them to multiple sections. Or maybe the other way around would make more sense, as we already have a Sections tab(?)
I can see it might also open up usabilty problems – for instance if you published an article and then changed it to a section with different custom fields, what would happen to the data in the custom fields that you’d saved. I’ve used Cute before, with the functionality we’re talking about here, and sometimes I would start to write an article in the default section, then realise I hadn’t set a Section value, and then lose what I’d typed when I applied one. So it would bring complications, but I’d still kill for it!
Offline
#17 2006-06-28 13:25:01
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: [request] "Cascading" custom fields.
pieman wrote:
can’t a man sit on the fence and cheer in peace these days? ;)
Well I kind of grasp the ‘cascade’ concept, but can’t really see the usefulness of specifying the contents of custom fields at a section/global level… couldn’t you can kind of do that already with <code><txp:if_custom_field name=“pies”><txp:custom_field name=“pies” /><txp:else />we’re all out of pies</txp:if_custom_field></code> in your form? Maybe I’m missing the point tho.. it happens!
Knew there was a good reason why no-one was shouting for this :O)
Thanks for the clarification!
Last edited by net-carver (2007-11-27 14:08:56)
— Steve
Offline
Re: [request] "Cascading" custom fields.
I think the cascading custom fields would be very powerful once sub-sections are in place with 4.1
Shoving is the answer – pusher robot
Offline
#19 2006-06-28 16:12:02
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: [request] "Cascading" custom fields.
Thanks Patrick! :O)
— Steve
Offline
Re: [request] "Cascading" custom fields.
<blockquote>pieman said…
I can see it might also open up usabilty problems – for instance if you published an article and then changed it to a section with different custom fields, what would happen to the data in the custom fields that you’d saved. I’ve used Cute before, with the functionality we’re talking about here, and sometimes I would start to write an article in the default section, then realise I hadn’t set a Section value, and then lose what I’d typed when I applied one. So it would bring complications, but I’d still kill for it!</blockquote>
Two things:
1) The custom fields for a particular section will be available only after we select that specific section (i hope i’m right). So I dont see a point here, unless I’ve misunderstood you pieman.
2) I bieleve that we usually dont change the section for an article. That’s why categories are in place.
Please correct me if I’m wrong here.
Regards,
Vasanth
Last edited by creativesplash (2006-06-28 16:58:20)
“Take a point, stretch it into a line, curl it into a circle, twist it into a sphere, and punch through the sphere.”
— Albert Einstein
Offline
Re: [request] "Cascading" custom fields.
Hello Vasanth
on point 1, true… that was just my experience from another CMS, but it could be avoided
on point 2, usually is the key word there… you’re right, but the site I’m building at the moment needs to do exactly that
these are all pretty hypothetical problems at the moment though
Last edited by pieman (2006-06-28 17:04:43)
Offline
Re: [request] "Cascading" custom fields.
hakjoon wrote:
I think the cascading custom fields would be very powerful once sub-sections are in place with 4.1
I completely agree with you. It could do miracles and save a lot of time.
pieman wrote:
these are all pretty hypothetical problems at the moment though
I quite agree with you. I may have sounded a bit rude so excuse me for that. I dint mean to be rude though.
My advice would be that you stick to changing categories instead of sections. I myself have come across such a problem, but have solved it by assigning a different category.
Anyway hypothetically speaking you never know. Maybe both categories are busy. Lets say the section has to be changed. My suggestion would be that the custom data should continue to be in the database. There should be a tag (may be <txp:custom_field name="blabla" section="blabla" oldsection="blabla2" />) or something like that to pull out the older custom field data. Just a suggestion though. There may be better ways to handle this issue.
Regards,
Vasanth
“Take a point, stretch it into a line, curl it into a circle, twist it into a sphere, and punch through the sphere.”
— Albert Einstein
Offline
Re: [request] "Cascading" custom fields.
pieman wrote:
I can see it might also open up usabilty problems – for instance if you published an article and then changed it to a section with different custom fields, what would happen to the data in the custom fields that you’d saved. I’ve used Cute before, with the functionality we’re talking about here, and sometimes I would start to write an article in the default section, then realise I hadn’t set a Section value, and then lose what I’d typed when I applied one. So it would bring complications, but I’d still kill for it!
I think if the custom field is of the same field type (text input in both sections for example) I think the custom could probably just remain through a change in section.
Switching from section that has custom1 as a text field to a section that has custom1 as a drop down is more complicated though. That will definitely need to be worked out.
Maintaining old records like Vasanth demonstrates however creates all sort of other complications.
Last edited by hakjoon (2006-06-28 23:57:39)
Shoving is the answer – pusher robot
Offline
Re: [request] "Cascading" custom fields.
Hello all,
Are any of these ideas still alive?
I sure hope so.
—
Tom
Offline