Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
While testing my plugin update I get:
Notice: Undefined variable: f in /blah.com/textpattern/lib/txplib_misc.php on line 144(and lines 147 & 153) in debug mode when trying to use dmp(). Has dmp() changed functionality in this release? Am I using it wrong now?
Last edited by Bloke (2008-01-30 00:30:09)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
Bloke wrote:
Has dmp() changed functionality in this release?
Yes, it optionally dumps to a file if you define('txpdmpfile', 'foobarbaz-you-name-it.txt'); before you call it.
Am I using it wrong now?
Not at all. This notice stems from an ommision which is already fixed.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
Thanks wet, good to know. That’s a useful feature.
Sorry about the duplication – I used the link in the first post to grab a newer version before I posted and it still exhibited the behaviour; thought it would be the most recent version, d’oh!
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
We do not update RCs with every fixed bug – there are no “nightlies”, just a single snapshot from Sunday.
Offline
#65 2008-01-30 12:36:54
- lee
- Member
- From: Normandy, France
- Registered: 2004-06-17
- Posts: 831
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
Even with glz_custom_fields: needs add_privs(‘glz_custom_fields’); custom fields are not showing in the write tab.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
lee, please contact the plugin author about this.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
Two more admin side related plug-ins that require an ‘add_privs’ fix, or similar, because of “Restricted Area’ issue under Extensions tab.
- stm_image_uploader
- fpx_image_import
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
joebaich wrote:
stm_image_uploader
Upgrade to version 0.4. That one has add_privs added. Not just for publisher, but for all levels.
fpx_image_import
Added to the opening post, thanks.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
I’m not sure if this is a 4.0.6rc issue or not. In case it is . . .
snv update:- Textpattern version: 4.0.5 (r2796)
- Last Update: 2008-01-31
- cnk_section_tree v.0.3 – installed on plugin, installed on Extension tab
- When activated, Write tab becomes essentially non-functional. See screenshot
Mike
Last edited by maverick (2008-01-31 20:08:00)
Offline
#70 2008-01-31 22:46:43
- FireFusion
- Member
- Registered: 2005-05-10
- Posts: 698
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
The latest version of jQuery is 1.2.2
Update!
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
Just installed TXP 4.06 (at http://yatil.de) and noticed following annoyances:
- TXP didn’t recognize my config.php
- Login worked but I had to clean my cookies
- After reinstalling TXP didn’t recognize my charset (utf-8). Everything worked fine before. This results in some ugly characters. I hope I haven’t to search-replace them…
A full diagnosis file can be found here: http://yatil.de/txpdiag.txt
Eric Eggert
Textpattern-Sites: yatil! | Snookerblog | Schachfreunde Ruhbank
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.6
Eric
- If config.php wasn’t recognized, you’d get database errors, because the username/password was unknown. Did that happen?
- Your diagnostics show that your tables are using a latin1 charset, so config.php should specify a dbcharset set to latin1. Does your config.php contain a dbcharset parameter and have you tried setting it to latin1?
- Where do you see the ugly characters, only on the text that is part of textpattern (like “Temporäres Verzeichnis:”) or also in the articles you wrote?
Offline