Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
makss wrote:
Why textpattern use only varchar(255) for custom fields and Keywords?
Most likely it was thought that more isnt needed and varchar is enough. If you need more options, you can always use unlimited custom fields.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Hi there..
I like this version very much, runs even faster than 4.0.8 (or is this just my imagination)!
Will there be a second or even a third release candidate or is the final version the next step? And will it be possible to upgrade smoothly from RC to final?
Thanks in advance for your answers.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
makss wrote:
Why textpattern use only varchar(255) for custom fields and Keywords?
If you google for the recommended length of the keywords meta tag, you’ll find that 255 chars is more than enough. The custom fields are <input type="text".. fields. Entering more than 255 chars in such a field is not practical, so in the database the size is limited to that value. DB fields shouldn’t be larger than necessary.
In unicode it’s 127 symbols…
Not true. Your assumption is that all chars take 2 bytes, which isn’t true in utf-8 (characters from us-ascii use 1 char, anything else 2 or more chars). And if you use utf-8 tables (you’re probably using latin1), which should happen automatically on fresh installs when using MySQL 4.1 or higher, varchar(255) really does mean 255 characters, even if they are multi-byte utf8 characters.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
lazyadmin wrote:
Will there be a second or even a third release candidate or is the final version the next step?
Judging by the current issues, the next release will be final. We have still one item to clarify, though, which might force a second RC.
And will it be possible to upgrade smoothly from RC to final?
Probably.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
I suggest you change it so 4.2rc identifies itself as such, and not 4.0.8. It seems me and a few others wasted some time trying to figure out what went wrong, myself downloading and installing twice, until I finally got smart and saw the little disclaimer at the bottom of the download page. Not everyone is as smart as me, and will figure it out as quick.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Textpattern FAQ will need an update soon.
Get all online mentions of Textpattern via OPML subscription: TXP Info Sources: Textpattern RSS feeds as dynamic OPML
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
merz1 wrote:
Textpattern FAQ will need an update soon.
Good call. And also possibly related Can Textpattern share a database because there’s now a third way to share a DB among Textpatterns under 4.2.0.
Last edited by Bloke (2009-08-09 19:29:13)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
One slight wibble with the plugin lifecycle management / default body ID mechanism. Consider smd_bio as an example. The admin hook for the plugin prefs is plugin_prefs.smd_bio. When clicking the ‘Options’ link I am transported to the given (tabless) page. The markup is rendered and the body tag contains this:
<body id="page-plugin_prefs.smd_bio">jQuery code such as this:
jQuery("#page-plugin_prefs.smd_bio .some_other_class") ...cannot target this ID because it thinks the .smd_bio part is a class reference and thus is trying to actually match:
<body id="page-plugin_prefs" class="smd_bio">Any way round this? (aside from not using the body ID attribute!)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
#100 2009-08-09 21:35:46
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Bloke wrote:
Any way round this? (aside from not using the body ID attribute!)
Core might want to use _ or - instead. Btw, doesn’t the selector also support escaping? Like:
jQuery("#page-plugin_prefs\\.smd_bio")Last edited by Gocom (2009-08-09 21:44:47)
Offline
#101 2009-08-09 22:01:31
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Bloke wrote:
doesn’t the selector also support escaping?
Probably! That would undoubtedly do the trick. Thanks Gocom, I shall RTFM :-)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
#102 2009-08-10 05:49:51
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
I am seeing strange RSS feeds on the TXP Tips site. Access either the Feedburner feed or the site’s own at “feed://txptips.com/rss/?section=articles” to see – the article excerpt displays the same excerpt for all the articles.
The blog feed is fine though..
Offline
#103 2009-08-10 06:17:08
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Funny – it fixed itself when I commented out lines 1171-1172 in include/txp_article.php that refer to pings.
Offline
#104 2009-08-10 06:53:57
- makss
- Plugin Author
- From: Ukraine
- Registered: 2008-10-21
- Posts: 355
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
jstubbs wrote:
I am seeing strange RSS feeds on the TXP Tips site. Access either the Feedburner feed or the site’s own at “feed://txptips.com/rss/?section=articles” to see – the article excerpt displays the same excerpt for all the articles.
The blog feed is fine though..
Another BUG in RSS/Atom feed with same simptoms. The article excerpt(or body) displays the same excerpt(or body) for all the articles in RSS/Atom feed.
BUG in RSS/Atom feed
Last edited by makss (2009-08-10 06:55:19)
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_dragdrop : Drag&Drop categories (article, link, image, file)
Offline
#105 2009-08-13 03:16:17
- kevinpotts
- Member
- From: Ghost Coast
- Registered: 2004-12-07
- Posts: 370
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
OK, installed RC on my development version of my blog, and noticed a few issues.
1.) Under Diagnostics, TXP is telling me files are out of date or modified even though they have been overwritten by the the newest versions. Specifically:
Some Textpattern files are out of date:
/home/.celine/graphicpush/dev.graphicpush.com/index.php
Some Textpattern files have been modified:
/home/.celine/graphicpush/dev.graphicpush.com/rpc/index.php2.) A lot of my old plugins are chucking wobblies left and right. My site has been around for years and this might be the equivalent of barnacles accumulating on an old hull, but for what it’s worth, the following have some kind of issue:
gho_comments_invite 4.0
nhn_livecommentpreview 0.3.1 (errors for this thing are all over the place in the admin section)
ako_social 0.4
gbp_permanent_links 0.11.617 (the admin side fails completely, but old rules still work)
glz_custom_fields 1.1.3 (seems to still work with articles, but admin side throws errors)
Oddly, all of these plugins work just fine in Live mode, even nhn_livecommentpreview, so I’m not sure how deeply to pursue this.
3.) It resent my URL mode from /title to /section/title. Once I changed it back, it was fine.
4.) Immediately got an error on using <txp:message />, but that was easily fixed to <txp:comment_message />. (Told you this site was old.)
5.) On my section landing pages (example 1, 2), I get this error in Live mode that disappears when you’re in Testing mode:
Strict Standards: Only variables should be passed by reference in /home/.celine/graphicpush/dev.graphicpush.com/textpattern/lib/txplib_misc.php(594) : eval()'d code on line 465I’m happy to provide more information on any of these issues if you want.
Last edited by kevinpotts (2009-08-13 03:17:59)
Kevin
(graphicpush)
Offline