glz_custom_fields

gerhard · 2009-10-09 12:28:38

mrdale wrote:

gerhard, can we twist your arm while we have your attention-ish to do another rev of glz with some of the simpler feature requests and bug squashies?

Hi Dale, I was planning a release this week, might need to wait until the next one though.

I have taken note of all the bugs that you’ve mentioned here and have addressed most of them, the most serious one has to do with deleting sequential custom sets. I’ve just sent an e-mail to Robert with a proposed solution, this is the gist of it.

In glz_custom_fields v1.2.2 I am no longer making a difference between 1-10 custom sets and the ones above that (e.g. custom_11_set, custom_12_set etc.). Since a user can adjust a custom set positioning, it makes no relevance whether that’s custom_5_set or custom_50_set. If custom_6_set is deleted, there will be an error because we’re using max_custom_fields to iterate over custom sets, when $i = 6, custom_6_set won’t be found . With my suggested changes, we could simply iterate over $prefs['custom']. This is what I’m proposing

This is an important change because this will open the floodgates for custom fields for other data types which I would like to see in the plugin before the end of this year : ).

redbot · 2009-10-09 13:35:29

gerhard wrote:

…I was planning a release this week, might need to wait until the next one though.

…This is an important change because this will open the floodgates for custom fields for other data types which I would like to see in the plugin before the end of this year : )

Thanks Gerhard for all your efforts! IMHO it is ok to wait a little more to have a more stable and cooler plugin. All in all the issue with sequential custom sets can be somehow managed untill the next version is out.

gerhard · 2009-10-09 14:02:30

I am starting to think that I might have rushed into removing the separation between 1-10 custom sets and the ones above. If I had kept the reset button rather than changing them all to delete/edit, you wouldn’t have had this issue in the first place. I might re-introduce the separation until we figure the $prefs namespacing with Robert.

Last edited by gerhard (2009-10-09 14:02:56)

mrdale · 2009-10-09 14:41:00

go go gadget gerhard. ;)

Zanza · 2009-10-13 08:40:53

Sorry, I have a problem with glz_custom_field latest version (1.2.2) and other plugins in txp 4.2.0. Especially:

bot_show_image is broken (the image is put below the table instead of its proper place above article image field)
~~jmd_image_selector is not showing the insert image link~~ works with most recent jmd plugin version!

They both look as jquery problems. Am I doing something wrong?

Last edited by Zanza (2009-10-13 10:43:14)

gerhard · 2009-10-13 09:01:43

Hi zanza,

there have been some jQuery issues in v1.2.2, I have fixed them, will be pushing the updated revision later on this week.

On another note, I’ve agreed with Robert about the $prefs approach, I’ll be sending a patch to the core this week, it’s going to be really helpful for other plugin authors. It won’t be available until the next TXP release (hopefully the minor one), so fingers crossed it will become available soon.

The next glz_custom_fields version due out this week is going to focus on bug fixes and improving the stability of the plugin before I will turn my attention into sed_section_fields integration.

Last edited by gerhard (2009-10-13 09:03:32)

Zanza · 2009-10-13 10:42:26

thanks Gerhard. I have to say that the issue is with bot_show_image only, at the moment, because the jmd image selector I was using was outdated. Waiting for the fix+patch, anyway. Thanks.

Last edited by Zanza (2009-10-13 10:49:32)

tye · 2009-10-15 06:11:57

Thanks Gerhard – a very timely release for my next project:)

Zanza · 2009-10-16 15:09:33

Hi Gerhard. I found that also the recent wet_quick_open is not working when your plugin is installed. Just to give some other hint to check. Thanks.

uli · 2009-10-16 19:49:00

I found that also the recent wet_quick_open is not working when your plugin is installed.

Zanza, Gerhard, I’ve these two installed and working.

FireFusion · 2009-10-19 07:10:48

Hi Gerhard,

any news on the patch?

Thanks.

jens31 · 2009-10-21 10:16:58

hi

i have a little issue, but maybe im handling it wrong:
i use a custom field (type select) and provide a default value using brackets.
when putting out my custom_field value on the website, the brackets will also appear.

thanks for the help
jens

uli · 2009-10-21 11:12:38

Jens, you can put another “bracket” around your custom field with rah_replace like that:

<txp:rah_replace from="{,}" to="">
	<txp:custom_field name="bracketed_cf_select" />
</txp:rah_replace>

jens31 · 2009-10-21 11:54:48

all right, will check this out.
danke sehr.

Edit:
thanks for the hint with that rah_replace plug-in. its the shiiiiiiiiiiiiiiiiit.

Last edited by jens31 (2009-10-21 15:08:35)

redbot · 2009-10-22 11:02:29

Hi Gerhard,
I need urgently to finish a project I’m working on but I’m stuck with the jquery problems you mentioned here which interfere with other jquery plugins. Is there a possibility you post here the necessary amendments to the code? I’m sorry to bother but I would really appreciate it (if you can of course).

Textpattern CMS

Textpattern CMS support forum

#526 2009-10-09 12:28:38

Re: glz_custom_fields

#527 2009-10-09 13:35:29

Re: glz_custom_fields

#528 2009-10-09 14:02:30

Re: glz_custom_fields

#529 2009-10-09 14:41:00

Re: glz_custom_fields

#530 2009-10-13 08:40:53

Re: glz_custom_fields

#531 2009-10-13 09:01:43

Re: glz_custom_fields

#532 2009-10-13 10:42:26

Re: glz_custom_fields

#533 2009-10-15 06:11:57

Re: glz_custom_fields

#534 2009-10-16 15:09:33

Re: glz_custom_fields

#535 2009-10-16 19:49:00

Re: glz_custom_fields

#536 2009-10-19 07:10:48

Re: glz_custom_fields

#537 2009-10-21 10:16:58

Re: glz_custom_fields

#538 2009-10-21 11:12:38

Re: glz_custom_fields

#539 2009-10-21 11:54:48

Re: glz_custom_fields

#540 2009-10-22 11:02:29

Re: glz_custom_fields

Board footer