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!
With another site today I copied the default stylesheet and named it “new”. After creation the stylesheet displays as the “default” sheet in the sense that it is not delete-able, although it is not yet in use by any section.
After then copying over the contents of “new” to default, then deleting “new” all returns to normal.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Minor cosmetic issue:
some submit buttons (for example, the “Save” or “Go” buttons on “Admin -> Preferences”) when clicked (so :focus or :active state are triggered) don’t look nice. They change to a pale yellow background over white text which makes it difficult to read.
(btw, I’m not sure if I’m on RC2, as this installation came from an SVN checkout. It’s rev 3250. So if this is already “fixed”, please, ignore this post)
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
maniqui wrote:
They change to a pale yellow background over white text which makes it difficult to read.
Strange. Doesn’t do it on my copy. But I have seen this behaviour before. Can you please check if it persists when you disable glz_custom_fields — from memory I think that does mess about with the colours of buttons and other input controls. Thanks.
Last edited by Bloke (2009-08-06 22:17:01)
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: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Hi Bloke,
well spotted!
glz_custom_fields is related to this issue.
Though, It’s weird that it doesn’t affect every “dark red” button… some are affected, some others aren’t.
Thanks.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
RSS-Atom bug
please, see it http://forum.textpattern.com/viewtopic.php?pid=212423#p212423
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
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
DB structure
CREATE TABLE `".PFX."textpattern [..skip...] `Keywords` varchar(255) NOT NULL default '', [..skip...] `custom_1` varchar(255) NOT NULL default '', `custom_2` varchar(255) NOT NULL default '', `custom_3` varchar(255) NOT NULL default '', `custom_4` varchar(255) NOT NULL default '', `custom_5` varchar(255) NOT NULL default '', `custom_6` varchar(255) NOT NULL default '', `custom_7` varchar(255) NOT NULL default '', `custom_8` varchar(255) NOT NULL default '', `custom_9` varchar(255) NOT NULL default '', `custom_10` varchar(255) NOT NULL default '',
Why textpattern use only varchar(255) for custom fields and Keywords? In unicode it’s 127 symbols…
I change Keywords to text and custom_1 – custom_10 to mediumtext
Tested on TxP 4.0.4 – 4.0.7 – all OK!
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
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