Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#421 2009-09-12 01:31:45
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,319
Re: glz_custom_fields
I don’t know whether this has been covered before or is even sorted out but I once noted these:
- Like Dale, I’m for a re-ordering mechanism for existing cf’s: Sites tend to change and grow.
- All kinds of inputs with more than one value are sorted alphabetically, not in the order they were entered.
- Copying existing sets would be very helpful, although probably out of scope.
- If you forget entering a cf name all typing is lost (“Ooops! custom set must have a name”). Shouldn’t it check for a name first and thus leave my work/text untouched? Easiest solution: put the text field for cf name last.
- Some improvements for trigger words:
- They shouldtn’t be shown above the menu (at least I don’t have a reason to show them)
- If someone needs them to be displayed: A possibility for a translation would be nice, a “range” is something completely different in German (romp). I tried to change something (don’t remember what exactly, but I think it was simply translating “range”), but obviously there’s a function counting the letters, so my results looked rather odd.
- Furthermore, showing the unit twice in each line of the menu is too much. glz_cf is for pampering my clients so everything should be easy to read and use, good looking, and clean.
Last edited by uli (2009-09-12 09:44:03)
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
#422 2009-09-12 07:21:29
- mlarino
- Member
- Registered: 2007-06-29
- Posts: 367
Re: glz_custom_fields
-ordering cf
-convination of sed_section_fields and glz_custom_fields in one plugin
-no alphabetical sorting option
-better searching
:)
Offline
#423 2009-09-14 15:31:42
Re: glz_custom_fields
+1 for textarea
Offline
#424 2009-09-18 19:36:31
Re: glz_custom_fields
Textarea would be great. Also been caught out a couple of times by entering data into CF fields, then choosing “html” or “preview” in the write tab. This results in whatever was entered into the CF being lost. Not a big deal really.
Any updates on progress with 4.2.0 compatibility?
Offline
#425 2009-09-18 19:55:01
Re: glz_custom_fields
renobird wrote:
+1 for textarea
+1
Offline
#426 2009-09-19 04:44:22
Re: glz_custom_fields
Any hacks for glz_custom_fields on TXP 4.2 floating around?
Don’t mean to sound to impatient before the next glz_custom_fields update. I have to make a choice in the next hour whether to make a huge merging of an old install with 4.2 or not. I hack would suffice if could be removed easily enough once made redundant.
txtstrap (Textpattern + Twitter Bootstrap + etc…)
Offline
#427 2009-09-21 01:40:03
- kevinpotts
- Member
- From: Ghost Coast
- Registered: 2004-12-07
- Posts: 370
Re: glz_custom_fields
+1,000,000,000 for 4.2.0 compatibility.
Kevin
(graphicpush)
Offline
#428 2009-09-21 02:20:22
Re: glz_custom_fields
I’ll see Kevin’s +1,000,000,000 – and raise it another.
glz_custom_fields is essential.
Offline
#429 2009-09-21 05:16:54
Re: glz_custom_fields
renobird wrote:
glz_custom_fields is essential.
Indeed!
txtstrap (Textpattern + Twitter Bootstrap + etc…)
Offline
#430 2009-09-21 13:31:26
Re: glz_custom_fields
I have been working away last week on the plugin, it’s almost ready to be e-mailed around, I just need to finish off replacing some of the javascripts which were manipulating the UI, pluggable_ui() has been a delight, thanks again Robert!
I’ve also made a post related to zem_tpl, the plugin had to be broken down into separate components because it was becoming too much to handle. Besides the massive re-organization, we now have improved installation & uninstallation routines, remove the plugin and it will leave your TXP database spotless, as if it wasn’t there : ).
The new plugin functions available in TXP 4.2.0 open the possibilities for some rather exciting stuff, expect some long overdue, highly sought for features to start trickling in.
ETA for a glz_custom_fields() compatible with TXP 4.2.0 is just a few days, there will be at least 1 new feature which will make it worth the wait.
Offline
#431 2009-09-21 13:41:32
Re: glz_custom_fields
Gerhard,
You RULE! Thanks for the update – looking forward to it.
:)
Offline
#432 2009-09-21 13:43:37
- jelle
- Member
- Registered: 2006-06-07
- Posts: 165
Re: glz_custom_fields
Thanks for all the hard work Gerhard…looking forward to the new glz_cf!
Offline
#433 2009-09-21 13:43:48
- masa
- Member
- From: North Wales, UK
- Registered: 2005-11-25
- Posts: 1,095
Re: glz_custom_fields
gerhard wrote:
ETA for a glz_custom_fields() compatible with TXP 4.2.0 is just a few days, there will be at least 1 new feature which will make it worth the wait.
Just curious, does that mean it won’t work with 4.0.8?
Offline
#434 2009-09-21 13:55:01
Re: glz_custom_fields
Hi all,
I’m just putting together a rather large site in textpattern (v4.2.0) and this plugin is going to be ideal. My question is, can I fill info into the vanilla custom fields now and then easily convert them when the plugin is available? Or would I have to input data into the fields all over again?
For example, I have one custom_field that at the moment I simply put a ‘y’ in if the page needs access to some javascript. Obviously a tickbox would better suit this task, but I have a few hundred articles so don’t want to re-do stuff if I don’t need to.
Thanks,
Phil
Offline
#435 2009-09-21 14:13:56
Re: glz_custom_fields
masa wrote:
Just curious, does that mean it won’t work with 4.0.8?
The new glz_custom_fields v1.2.2 will have TXP 4.2.0 as the minimum requirement. v1.2.1 will be the last version that will work with TXP 4.0.8.
philwareham wrote:
can I fill info into the vanilla custom fields now and then easily convert them when the plugin is available?
One of the installation routines is to convert all your existing custom field data. By default, it will convert the existing custom sets to “selects” and it will save all unique values across each article. An example might explain this better.
Let’s say you have custom_set_1 defined as “Highlight” in Custom Fields (advanced prefs). For article_1, “Highlight” is “y”, for article_2 it is “n” and for article_3 it is “y”. When you install glz_custom_fields, custom_set_1 will become of type “select” with 2 possible values, “y” & “n”. The same happens for every custom set, only values will differ. Hope that helps!
Offline