Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#136 2008-02-09 12:10:58
Re: glz_custom_fields
Nope, TXP diagnostics report PHP version: 5.2.5. I’m on a Joyent Shared Accelerator so it’s pretty up-to-date.
Offline
#137 2008-02-09 12:51:35
- redbot
- Plugin Author
- Registered: 2006-02-14
- Posts: 1,410
Re: glz_custom_fields
I’m sorry then, I have no idea what it can be. Hope someone can give better advice
Offline
#138 2008-02-10 06:53:20
Re: glz_custom_fields
Nick, email me (mmanfre on gmail) the plugin and I’ll send back a fix.
Offline
#139 2008-02-10 14:05:27
Re: glz_custom_fields
After hours of frustration, I am drawing the line, it’s too much hassle to go around a few lines of code which should be in TXP’s core. Right now the plugin has over 500+ lines of redundant code because of the infamous getCustomFields() which imposes a hard, 10 limit to custom fields. We currently have that glz_custom_fields_article() function which takes care of lists of articles and our custom search, but the problems you have been experiencing with single articles not displaying the custom fields > 10 is related to the preText() function which runs deep, it produces a global available on every single page and yes, it uses getCustomFields(). There might be a way of adding to the array this function puts into GLOBALS, but I don’t have the time to figure this out right now. I remember trying this approach in the past, but because of the sequence of function calls, it’s not always guaranteed that what you are setting in the GLOBALS will be available in the final output.
I would have really liked to release v 1.1 this weekend with all the features on the roadmap – last weekend was just impossible – but I have to disappoint. There have been a tonne of really good contributions and a lot of guys which helped in all the little ways, but I simply didn’t have the time to roll out all the features promised for 1.1. )Actually, the features for 1.0 because I have decided to stop the BETA madness and the first release ever will have been 1.0, this one 1.1 etc.)
I am packaging what I have and putting it out as 1.1, there have been enough little hacks and fixes over the last few weeks, it’s time to have them as part of the main plugin.
I really don’t know when 1.2 will be out, but things should clear up over the next few weeks, this winter was really crazy…
Last edited by gerhard (2008-02-10 14:06:11)
Offline
#140 2008-02-10 14:15:44
- lee
- Member
- From: Normandy, France
- Registered: 2004-06-17
- Posts: 831
Re: glz_custom_fields
Hi Gerhard, thanks for the update, when roughly do you expect to release 1.1?
Cheers, Lee.
Offline
#141 2008-02-10 14:18:06
Offline
#142 2008-02-10 14:23:41
- lee
- Member
- From: Normandy, France
- Registered: 2004-06-17
- Posts: 831
Re: glz_custom_fields
Cool, thanks for clarifying.
Offline
#143 2008-02-10 14:48:21
- redbot
- Plugin Author
- Registered: 2006-02-14
- Posts: 1,410
Re: glz_custom_fields
Thanks for your work Gerhard!
I agree with your decision to release v1.1 even if it comes without all the features in the roadmap.
It will bring anyway some new features so -at least for now – I’ll be happy with it …and in meantime I’m sure we will find some ‘dirty’ way to overcome the current limitations.
Not to mention we could use it in combination with another great plugin (sed_section_fields)
Offline
#144 2008-02-10 17:16:24
Re: glz_custom_fields
Thanks Gerhard!!.
Offline
#145 2008-02-10 17:48:58
Re: glz_custom_fields
Gerhard,
What is the proper way to upgrade? Any particular things that could happen and should be avoided?
Offline
#146 2008-02-10 17:51:51
- lee
- Member
- From: Normandy, France
- Registered: 2004-06-17
- Posts: 831
Re: glz_custom_fields
I just upgraded an ultra basic test site and the search result tag isn’t spitting anything out anymore – it was before. Looking into it now…
Last edited by lee (2008-02-10 17:52:14)
Offline
#147 2008-02-10 21:08:16
- jelle
- Member
- Registered: 2006-06-07
- Posts: 165
Re: glz_custom_fields
jstubbs wrote:
Gerhard,
What is the proper way to upgrade? Any particular things that could happen and should be avoided?
Hi jstubbs,
Here a quote from Gerhards e-mail to all the plugin contributers:
You can easily replace the previous version, just delete that one and re-upload & activate this one. For safety measures a database back-up before upgrading is recommended.
Offline
#148 2008-02-10 22:59:01
Re: glz_custom_fields
I tried to install and got the following error message: “Badly formed or empty plugin code.”
Offline
#149 2008-02-10 23:31:35
- shi
- Member
- Registered: 2005-12-09
- Posts: 34
Re: glz_custom_fields
This might be a beginner question…
Is there a way of displaying Custom Fields tab under Extensions tab if you are not administrator (publisher)? Managing editor for example…
Now I can only see Custom Fields tab if I log as a Publisher, but I want to enable other registered users to edit custom fields as well…
Offline
#150 2008-02-11 01:21:39
Re: glz_custom_fields
Hey everyone,
NickCaldwell wrote:
I tried to install and got the following error message: “Badly formed or empty plugin code.”
That has to do with the upload limit on your PHP install. Find php.ini and set the following: upload_max_filesize = 10M . Let me know if it helps. Also, you might be having issues with the max memory allocated for each script (less common though). Don’t forget that you need to set the upload limit in TXP as well (Admin > Preferences > Advanced). Anyone else experiencing a similar issue?
lee wrote:
I just upgraded an ultra basic test site and the search result tag isn’t spitting anything out anymore – it was before. Looking into it now…
Hmmm, let me know how that goes.
shi wrote:
Is there a way of displaying Custom Fields tab under Extensions tab if you are not administrator (publisher)? Managing editor for example…
OK, that is the new feature that was introduced in TXP 4.0.6 and “broke” the way the plugin was called. In the plugin code, look for add_privs('glz_custom_fields', '1'); and change to add_privs('glz_custom_fields', '1,2');. That will enable both the Publisher AND the Managing Editor to use the plugin. If you go over 2 (meaning under Managing Editor etc.), you might need to modify textpattern/lib/admin_config.php as well (starting around line 185), because the Extensions tab is only available to those 2 users by default.
Any more issues guys, let me know ; ).
Offline