glz_custom_fields_public
glz_custom_fields_public copied to clipboard
gerhard
glz_custom_fields contributors can raise bugs here and vote for features
If the page contains a checkbox custom field with selected values the Textpattern doesn't submit form.
This affects 1.2.4 and 1.3.0. Basically, on a multi-select created, the function `glz_selectInput` adds an empty first option (unless you pass the `$default_value` parameter as `true`, which doesn't seem correct...
While investigating [this bug](https://github.com/gerhard/glz_custom_fields_public/issues/29), I noticed that there is some kind of flaw in the logic behind the inclusion (or not) of a first empty option on single selects and...
This issue is very similar to [issue 23](https://github.com/gerhard/glz_custom_fields_public/issues/23), which was solved by the most recent upgrade. Now, instead of seeing a duplicate Excerpt field, the Body field is duplicated. The...
When someone changes the date format in the drop-down, the start date changes automatically to the new format.
Rather than cramming everything under Advanced Options, create a new, user-defined heading. The user will decide which custom fields to put where.
The plugin doesn't support any internationalisation at the moment. Use sed_section_fields as the starting point and implement MLP compatibility you slacker! : )
On the frontend, I’d like a dropdown for the customer to select a size http://gist.github.com/245088 Thanks kemie, great idea!
Set delimiter in plugin preferences for custom field values. Default is | Required by [_alan_](http://twitter.com/_alan_/status/6496720941)