Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2007-06-11 12:24:01
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,306
Consequent naming of attributes/values
I saw in Textbook that future versions of tags will only have values of “1” instead of “y” and “yes” or such. I really welcome this!
I’m posting here to remember that there’s a similar inconsequence in the naming of some attributes: there’s custom_1 but category1.
I’d appreciate very much if this would get adapted, too.
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
#2 2007-06-11 12:27:36
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: Consequent naming of attributes/values
…there’s a similar inconsequence in the naming…
I’m not exactly sure what you mean, but I gather from what else you said that you think we should do away with names like custom_1 and category1? If so, then yes, that will happen eventually.
Offline
#3 2007-06-11 12:42:14
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,306
Re: Consequent naming of attributes/values
Mary:
… should do away with …
Sorry, but my english …
What I mean is eiter category1 + custom1 OR category_1 + custom_1.
Last edited by uli (2007-06-11 12:42:39)
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
Re: Consequent naming of attributes/values
That is not likely to change in the 4.0.x series, otherwise things would break when upgrading existing TXP installs. Category1/2 will probably disappear in the 4.1 series of TXP if we switch to unlimited categories.
Offline