glz_custom_fields

Bloke · 2017-02-10 12:01:13

Try version 1.5.0-beta.1. Should fix any MySQL/4.6.2 issues. Please let me know otherwise.

phiw13 · 2017-02-10 13:43:27

Bloke wrote #303945:

Try version 1.5.0-beta.1. Should fix any MySQL/4.6.2 issues. Please let me know otherwise.

Double quick test: no more noise when creating a custom field! The custom textarea on the Write panel now works fine. I’ll test a little more tomorrow morning.

Thanks for the quick turnaround!

GugUser · 2017-02-10 14:33:03

Thanks for the survival help for this very useful plug-in!

GugUser · 2017-02-10 17:37:40

Oh fright, the 1.5.0-beta.1 plugin has converted all existing custom fields from type textarea to select with the values from all existing entries.

phiw13 · 2017-02-11 08:59:19

GugUser wrote #303956:

Oh fright, the 1.5.0-beta.1 plugin has converted all existing custom fields from type textarea to select with the values from all existing entries.

ouch, that is not nice :-(

Meanwhile, I’ve tested this on a fresh install, everything seems to perform well.

Also, some improvements to the plugin panels, to bring it more inline with Textpattern 4.6 and responsive design: I’ve used rvm_plugin_diff to generate a diff of the plugin code;
download (contains 2 files: a diff of the plugin code and a diff of the main glz_* stylesheet).

Changes:

removed the width/height constrains on the textarea
put the width of input[type=text] fields inline with others in the sidebar
reworked the Options panel for the plugin, matching Textpattern preferences
improved the form display at the bottom of custom fields extension panel.

Bloke · 2017-02-11 09:40:06

GugUser wrote #303956:

Oh fright, the 1.5.0-beta.1 plugin has converted all existing custom fields from type textarea to select with the values from all existing entries.

Gerhard’s 1.4.0 would have done the same. I didn’t change any of the code in relation to functionality, just fixed errors and warnings for MySQL/Txp 4.62. Not that it helps you, but I don’t know why it would change existing fields. Odd.

phiw13 wrote #303964:

some improvements to the plugin panels

Brilliant, thanks so much. I’ll download it and play.

jpdupont · 2017-02-11 16:08:45

Same problem (existing CF to select …) as GugUser, on a site in construction with last 4.7.0 dev.

GugUser · 2017-02-11 20:24:06

I can vaguely remember that I had this before, maybe with an update from 1.3 to 1.4. I think, according to Bloke’s answer, it must be a problem with glz_custom_fields itself.

phiw13 · 2017-02-14 01:49:55

When installing this plugin on one of my personal sites, I ran into a little snag. The associated stylesheet and JS file wouldn’t load. The site runs under https with rather restrictive CORS headers.

The problem is that the plugin hardcodes the protocol for the /path/to/stylesheet (and /path/to/javascript). The fix is simple; open the plugin for editing, search for http:// and replace with // (it is around line 1128 for the .css file and line 1175 for the .js file.

Edit: Or would it be better to use '.hu.' here ?

-   $css = '<link rel="stylesheet" type="text/css" media="all" href="//'.$prefs['siteurl'].'/plugins/glz_custom_fields/glz_custom_fields.css">'.n;
+   $css = '<link rel="stylesheet" type="text/css" media="all" href="'.hu.'plugins/glz_custom_fields/glz_custom_fields.css">'.n;

And the same for the javascript file.

That works on my local install at least.

Last edited by phiw13 (2017-02-14 02:46:40)

GugUser · 2017-02-14 02:36:25

Ah! Now I understand why suddenly the look was different. Thank you.

phiw13 · 2017-03-23 09:04:56

After a recent commit¹ on the TXP4.7-dev branch I had an annoying surprise, in that all the core custom fields where sort of disabled. That is, they displayed in the Write panel as Type not supported. It goes without saying that their values where not passed when needed.

I could fix it by going in the glz_custom_fields admin panel and re-saving each one of them (Edit button, save – 10 times). Saving on the Preferences panel had no effect.

That is the kind of thing that worries me when using those not-really-supported-anymore extensions… This extension still “works”, enough at least for my humble needs.

¹ I suspect this is a consequence of makss large patch. Perhaps he or Stef can explain.

Bloke · 2017-03-23 10:42:06

phiw13 wrote #304993:

After a recent commit on the TXP4.7-dev branch I had an annoying surprise, in that all the core custom fields where sort of disabled.

Eeek. Not good. Will have to set up a site that uses glz_cf in 4.6.2 and perform an upgrade to see if we can locate where this is going wrong. Although we don’t officially support plugins on upgrade and bend to their whims (caveat utilitor and all that), if we can avoid breaking something such as this plugin, then we should do so.

Textpattern CMS

Textpattern CMS support forum

#1153 2017-02-10 12:01:13

Re: glz_custom_fields

#1154 2017-02-10 13:43:27

Re: glz_custom_fields

Bloke wrote #303945:

#1155 2017-02-10 14:33:03

Re: glz_custom_fields

#1156 2017-02-10 17:37:40

Re: glz_custom_fields

#1157 2017-02-11 08:59:19

Re: glz_custom_fields

GugUser wrote #303956:

#1158 2017-02-11 09:40:06

Re: glz_custom_fields

GugUser wrote #303956:

phiw13 wrote #303964:

#1159 2017-02-11 16:08:45

Re: glz_custom_fields

#1160 2017-02-11 20:24:06

Re: glz_custom_fields

#1161 2017-02-14 01:49:55

Re: glz_custom_fields

#1162 2017-02-14 02:36:25

Re: glz_custom_fields

#1163 2017-03-23 09:04:56

Re: glz_custom_fields

#1164 2017-03-23 10:42:06

Re: glz_custom_fields

phiw13 wrote #304993:

Board footer