glz_custom_fields

mrdale · 2011-09-29 16:42:26

Here’s an idea that’s beyond my capabilities.

A custom field that uses a custom script to geocode an address (existing custom fields) in the current article and outputs those geocodes to itself in the form of a text field.

The obvious benefit is that an article can have googlemaps geocode it’s location only once, therefore making any map functions faster and more reliable that geocoding on the fly.

I found this resource on using php to geocode and insert the values into a table, but I’m not smart enough to bend it to the following purpose…

Grab the address fields from CFs in the existing article

Concatenate those fields into a single string

Feed that string to the google geocoder

Obtain XML or csv values

Drop the non-pertinent parts

present those values as an editable string if the field is empty.

so… looks straightforward, but it’s way outside of my capabilities. Anyone bored? {he laughs}

uli · 2011-10-05 23:41:21

Hi Gerhard,
I think it’d be great to have the actual custom fields’ numbers displayed in the Custom Fields tab for when you need to look up field’s numbers ( sort="custom_n" ). I know it’s visible when I edit a field, but it can need many clicks to get the correct one. E.g. at the moment I needed it to reconstruct bot_wtc rules from an SQL export file. (Yes, cool job.)
Probably needs you seconds to implement, and could be a time saver for many of us. Horizontal space seems to be sufficient.

Then I just realized there’s a stumbling block in v1.3.0:
Up to (and including) v1.2.4 the INSTALL.txt file told to put scripts in a folder called “scripts”. From v1.2.5 on it was named “plugins”. If on an update you continue putting scripts into the scripts folder, knowing you simply have to adapt paths in the plugin prefs, you’ll nonetheless end with a custom_fields tab that’s not working cause both paths to glz_custom_fields.js and glz_custom_fields.css have “plugins” coded in the plugin.

andreas · 2011-10-24 06:42:26

With version 1.3 of the plugin, this is what my custom field overview page looks like:

What can I do about it?

jens31 · 2011-10-24 08:54:34

to me this looks a little like you’ve installed another admin theme, right?
(just to isolate the problem)

tye · 2011-10-24 08:59:33

Or is it not seeing the glz_custom_fields.css… I think the folder changed from ‘scripts’ to ‘plugins’ in this upgrade, or just check to see if you uploaded it

andreas · 2011-10-24 09:15:43

jens31 wrote:

to me this looks a little like you’ve installed another admin theme, right?
(just to isolate the problem)

I used “Remora” the newer one of the two that come pre-packed with TXP. I just changed back to the classic theme but the problem remains.

andreas · 2011-10-24 09:23:53

OK – solved it. I re-uploaded both the plugin and the support folder and now it works on both admin-themes.

There doesn’t seem to be a file called glz_custom_fields.css – the CSS for the plugin, if I get this correctly, is packacked in the plugin code.

Thanks for your help.

Last edited by andreas (2011-10-24 09:24:36)

Algaris · 2011-11-01 08:20:00

For some reason whenever I try to add a new Text Area using glz_custom_fields I keep getting the following error.

Warning: BLOB/TEXT column 'custom_10' can't have a default value ALTER TABLE `textpattern` MODIFY `custom_10` TEXT NOT NULL DEFAULT '' in C:\wamp\www\my-site\textpattern\lib\txplib_db.php on line 89

Algaris · 2011-11-03 15:19:34

I’ve noticed that if I ignore the above error message I still get the text area in the Write tab. However I found when adding a lot of text (such as an HTML table) I get the following error message:

Warning: Data too long for column 'custom_10' at row 1 update textpattern set Title = 'Article-Title', Body = 'body-text' C:\wamp\www\mysite\textpattern\lib\txplib_db.php on line 89

Just so you know I’ve changed the Title, Body and site name in the generated error.

— Edit —
Just noticed when I get this error message all of the text I’ve entered into the custom field vanishes. Argh!

If it helps I’m using v1.3.0

Last edited by Algaris (2011-11-03 15:27:22)

maruchan · 2011-11-03 19:44:16

Do you have PHPMyAdmin? You could try changing that field to mediumtext or longtext.

Algaris · 2011-11-04 08:22:42

I do but was unsure where to look for it. I tried looking before posting here and found the custom_fields table but all I could see there were entries for custom_2_set.

redbot · 2011-11-04 09:05:13

Algaris wrote:

I do but was unsure where to look for it. I tried looking before posting here and found the custom_fields table but all I could see there were entries for custom_2_set.

Hi,
you must change the value in the “textpattern” table for column custom_2

Textpattern CMS

Textpattern CMS support forum

#949 2011-09-29 16:42:26

Re: glz_custom_fields

#950 2011-10-05 23:41:21

Re: glz_custom_fields

#951 2011-10-24 06:42:26

Re: glz_custom_fields

#952 2011-10-24 08:54:34

Re: glz_custom_fields

#953 2011-10-24 08:59:33

Re: glz_custom_fields

#954 2011-10-24 09:15:43

Re: glz_custom_fields

#955 2011-10-24 09:23:53

Re: glz_custom_fields

#956 2011-11-01 08:20:00

Re: glz_custom_fields

#957 2011-11-03 15:19:34

Re: glz_custom_fields

#958 2011-11-03 19:44:16

Re: glz_custom_fields

#959 2011-11-04 08:22:42

Re: glz_custom_fields

#960 2011-11-04 09:05:13

Re: glz_custom_fields

Board footer