glz_custom_fields & jquery

gesiwuj · 2008-07-07 09:03:55

I’ve recently installed glz_custom_fields (after reluctantly paying £10) but when enabled, any page I visit (whether user-end or back-end) merely shows this message;

Upgrade TXP to at least 4.0.5 or put jquery.js in your /textpattern folder. jQuery website

However, I’m using 4.0.6 which had jquery.js anyway… I even tried using the version from the website but the message still persists. Perhaps it’s because I’m using a local server with a virtual host (like in the Textpattern Solutions book)…

I’ll be grateful of any help. Thankyou in advance :)

PS. TextPattern is a very good piece of kit (well, once you get past the confusing naming of structural elements).

redbot · 2008-07-07 10:29:50

Yes, this is a very annoying problem (already discussed here).
Hope Gerhard will be back soon and fix this.

P.S.
maybe you should post this in the glz_custom thread so he will likely read it

juanjonavarro · 2008-07-07 10:42:21

You can just deactivate the jquery detection mechanism of the plugin. Look for the line:

if ( !file_exists($GLOBALS['txpcfg']['txpath'].'/jquery.js') ) die(glz_custom_fields_gTxt('jquery_missing'));

…and comment it.

redbot · 2008-07-07 11:05:55

juanjonavarro wrote:

You can just deactivate the jquery detection mechanism of the plugin…

Thanks for the advice. It will come useful

maniqui · 2008-07-07 15:32:40

gesiwuj wrote:

(after reluctantly paying £10)

I would like to know why.
Plug-in authors are free to get paid for their plug-ins, although they must release them under the GPL license.
Also, if I’m not wrong, an plug-in owner (someone who has paid for the plug-in) also is free to ask for some money for sharing the plug-in (they may be putting a price for making it available online, not for the plug-in itself) but this owner must also release it under the GPL license.

You could have ask any other user of glz_custom_fields if he/she was willing to share it with you.

And also, if you have paid for something that isn’t working for you, probably you can ask for support to the one who sold it to you, particularly if you buy it directly from the plugin’s author.

mrdale · 2008-07-07 15:46:30

maniqui wrote:

Plug-in authors are free to get paid for their plug-ins, although they must release them under the GPL license.

Supply and demand. Make something really useful and people are happy to pay. Personally I don’t have a problem with it, which is why I sponsored the development of an image selector recently. We had needed one for literally years, and the community-driven way wasn’t producing one. I offered money, others joined in, and literally, within a few days we had a great solution. Kudos JMD.

Kudos to netcarver too, with whom I’ve had a similar experience creating sed_anon_upload.

I don’t mind paying $20 to gerhard for a plugin that together with sed_section_fields essentially provides custom content types… something I’ve been furiously throwing pom poms in the air for, for literally years without result.

I guess sometimes a little cash gets people over the tipping point. Not that I’d want this to become the rule, mind you.

[edit] A new record for usage of ‘literally’ (x3) in a post… I’m literally exhausted.

Last edited by mrdale (2008-07-07 15:48:05)

masa · 2008-07-07 16:14:45

mrdale wrote:

I don’t mind paying $20 to gerhard for a plugin that together with sed_section_fields essentially provides custom content types […].

Would you mind explaining a bit more how you use this combination and what you mean by “custom content types”? It sounds interesting and perhaps I’m missing something here.

I have glz_custom_fields and can see how you can use sed_section_fields to load different sets of custom fileds in the write screen based on the section, but is there something more to it?

mrdale · 2008-07-07 16:51:19

masa wrote:

Would you mind explaining a bit more how you use this combination and what you mean by “custom content types”?

I’m using “custom content types” pretty loosely here… Most of the time you want to have a different set of fields for different areas of you site. For 90% of the work I do, having unlimited fields with a vaiety of datasets and selects, that can be grouped in a section-specific way is all I need.

<!— Theoretical ideal and basis for the original xPattern idea follows: leaving reality —>

The next step beyond this of course is an ability to have a content-agnostic “article” tag that can pipe lists through forms. So “image”, “person” and “building” would work exactly like “article”. Furthermore “true” custom content types could have “associated” or “nested”;

association: “group” might have a field where you could multi-select existing “persons”.
nesting: “doctor” might include the “person” subset of fields, but also include “research” and “education” fields.

gesiwuj · 2008-07-08 09:03:33

Thankyou very much for the replies! You’re certainly more helpful than the Wordpress community (my previous “CMS” of choice)!

@redbot – Sorry, I didn’t know there was a thread specifically for glz_custom_fields… I’m new to the Textpattern community and this forum!

@juanjonavarro – Thankyou, that seems to be working at the moment. Are there any functionalities of glz_custom_fields that would require jQuery and not function (properly)?

@the rest – I didn’t particularly mind paying £10 but it did throw me a little at first (especially since my website is not-for-profit) but the plugin seems great. It was just a small tongue-in-cheek comment :)

juanjonavarro · 2008-07-08 09:08:59

gesiwuj, glz_custom_fields requires jQuery. This workaround just deactivate the jquery detection mechanism (because it is not working on your host). But the plugin still uses jquery, which is actually installed with textpattern.

redbot · 2008-07-08 09:13:02

gesiwuj wrote:

Are there any functionalities of glz_custom_fields that would require jQuery and not function (properly)?

The plugin relies interely on jquery but juanjonavarro’s suggestion only deals with the jquery detection mechanism.
So the imporatant thing is that you have jquery in his place given that it’s only the detection mechanism that’s causing problems

edit: Oops! Juanjo was faster than me

Last edited by redbot (2008-07-08 09:15:12)

jakob · 2008-07-08 09:42:06

something I’ve been furiously throwing pom poms in the air for, for literally years

love that description ! I am so with you there!

Last edited by jakob (2008-07-08 09:42:16)

gerhard · 2009-03-09 07:13:51

Hi all, I have replied to this issue you were having in the original thread.

gesiwuj wrote:

I’ve recently installed glz_custom_fields (after reluctantly paying £10)

There has been enough talk about this, I feel I need to set a few things straight. glz_custom_fields is not the first TXP paid-for plugin. It’s different from other paid-for TXP plugins because there isn’t a ransom for it, it’s a one off donation that will give you the right to use it on as many websites as you want and will ensure you get updates for life.

If you pay for something – even if just a small amount – you get to value it more. Not that glz_custom_fields wouldn’t have an inherent value, but not getting something for free does put it in a different league.

How many TXP plugins are out there that got lost along the way or that have been ransomed, got to a particular revision and then the developer stopped working for them? I didn’t want glz_custom_fields to become one of those plugins. Even though I’m using PHP these days only because of this plugin, I am doing so because all you guys have contributed to this code and because it is my part of the deal to keep it going. Also, in all fairness and honesty, £10 can get you a few cups of coffee that I’m sure this plugin is going to save you in the long run. Not to mention that most of you are using TXP to build websites for various clients, £10 is not going to be a deal-breaker, right?

When all is said and done, it’s up to you to decide whether you pay for it or not. You most definitely don’t have to, you can still use TXP without it. I have spent plenty of time on this plugin to get it just right as to be entitled to ask for a small donation, otherwise I would have thought “that was a good experience, let’s move on”.

So, just as all good things are not free in life, just think of this as being one of those things : ).

mrtunes · 2009-03-24 01:50:29

hi gerhard. i tried installing your version of txp, also edited the file with the config-dist change, but i still get:
“ Upgrade TXP to at least 4.0.5 or put jquery.js in your /textpattern folder. jQuery website “

gerhard · 2009-03-24 07:02:35

Hi Elliott, I don’t think I have shared one of the early versions of glz_custom_fields v1.2 with you. The changes that have fixed this issue are not in my version of Textpattern but in the new plugin code. I am in the final stages of releasing it, we’re talking days.

Textpattern CMS

Textpattern CMS support forum

#1 2008-07-07 09:03:55

glz_custom_fields & jquery

#2 2008-07-07 10:29:50

Re: glz_custom_fields & jquery

#3 2008-07-07 10:42:21

Re: glz_custom_fields & jquery

#4 2008-07-07 11:05:55

Re: glz_custom_fields & jquery

#5 2008-07-07 15:32:40

Re: glz_custom_fields & jquery

#6 2008-07-07 15:46:30

Re: glz_custom_fields & jquery

#7 2008-07-07 16:14:45

Re: glz_custom_fields & jquery

#8 2008-07-07 16:51:19

Re: glz_custom_fields & jquery

#9 2008-07-08 09:03:33

Re: glz_custom_fields & jquery

#10 2008-07-08 09:08:59

Re: glz_custom_fields & jquery

#11 2008-07-08 09:13:02

Re: glz_custom_fields & jquery

#12 2008-07-08 09:42:06

Re: glz_custom_fields & jquery

#13 2009-03-09 07:13:51

Re: glz_custom_fields & jquery

#14 2009-03-24 01:50:29

Re: glz_custom_fields & jquery

#15 2009-03-24 07:02:35

Re: glz_custom_fields & jquery

Board footer