Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Last pre-release: 4.0.4rc1
The final/official release is scheduled for the first half of next week – unless unexpected problems/errors are detected. We would like to get feedback on clean installations and updates (and any problems you encountered). We will use the next days to get the history.txt and the release notes ready – if you can spot things that we forgot to mention in History.txt, feel free to help us fill in those blanks. :)
Known Problems:- The Opera+funny character problem on “content > comments” will be fixed for final in some way (also see my last comment in the previous thread).
- The version number in this rc still shows 4.0.3 – this is intentional.
If you are hesitant about updating a live site, that’s fine, wait a few more days for the official release. ;)
Download:
removed
Last edited by Sencer (2006-10-17 13:34:18)
Offline
#2 2006-10-07 15:31:43
- masa
- Member
- From: Asturias, Spain
- Registered: 2005-11-25
- Posts: 1,091
Re: Last pre-release: 4.0.4rc1
Is there an official listing, which plug-ins work or have been updated to work with 4.0.4?
I only use very few, but each of them is critical.
Cheers Martin
Offline
Re: Last pre-release: 4.0.4rc1
Hi Martin, we developers obviously do not have the resources/manpower to test all plugins and to maintain a compatibility list. However there have been efforts by lots of other people in that direction. AFAI am aware that information resides in Textbook:
http://textpattern.net/wiki/index.php?title=Plugin_Archive
(When you click through to the actual lists of plugins, you can see compatibility information)
It would be great if you, and people with similar concerns like yours, would help with that effort. On our part we’ve taken plenty of steps to give all plugin developers information ahead of time on potential compatibility issues, and that we are open to making changes to avoid those, if they arise and necessary changes were reasonable.
Having said that, with all of our maintenance releases (i.e. currently every official 4.0.x release) we take great care in not breaking backwards compatibility, and having smooth update paths. More so, than plenty of other opensource packages I am aware of. And we of course welcome everybody that is willing to help us with this.
Offline
#4 2006-10-07 16:07:36
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: Last pre-release: 4.0.4rc1
Most plugins will work the same. Some admin-side plugins might not (like mine).
Like most plugin authors (I think…) I’d wait until 4.0.4 was released, then post a simple update to make it work again.
Offline
#5 2006-10-07 16:40:51
- masa
- Member
- From: Asturias, Spain
- Registered: 2005-11-25
- Posts: 1,091
Re: Last pre-release: 4.0.4rc1
Sencer wrote:
AFAI am aware that information resides in Textbook:
Thanks, I hadn’t come across that one.
It would be great if you, and people with similar concerns like yours, would help with that effort.
I’ll give 4.0.4 a try when it comes out. I’m by no means a very sophisticated txp user, but I’ll install the plug-ins I usually employ and will report back in case I notice anything.
Cheers Martin
Offline
#6 2006-10-07 23:55:40
- zem
- Developer Emeritus
- From: Melbourne, Australia
- Registered: 2004-04-08
- Posts: 2,579
Re: Last pre-release: 4.0.4rc1
I’ll give 4.0.4 a try when it comes out. I’m by no means a very sophisticated txp user, but I’ll install the plug-ins I usually employ and will report back in case I notice anything.
We need to hear about problems before the 4.0.4 release, not after. That’s the purpose of the RC1 pre-release.
Alex
Offline
Re: Last pre-release: 4.0.4rc1
One thing I’ve noticed…If you have an article category which contains a single quote (‘), it will lead to javascript errors within the poweredit function on the content > articles tab.
The errors appear to come from lines 122 and 127 of txplib_head.php.
Offline
Re: Last pre-release: 4.0.4rc1
I noticed one thing that seemed kind of odd.
Copy a style and the current style in the window is changed to the new one.
Copy a template and you continue to edit the original.
Either way could make sense but it would be better for it to to behave consistently.
Offline
Re: Last pre-release: 4.0.4rc1
@wilshire, a patch that fixes the javascript errors (and a few other things as well) was posted to txp-dev on september 17th. => already fixed now.
Last edited by ruud (2006-10-09 22:52:31)
Offline
Re: Last pre-release: 4.0.4rc1
michaelkpate wrote:
Copy a style and the current style in the window is changed to the new one.
Yeah, I noticed that too. I hope the first behavior (copy>copy loaded) is used for both pages and styles.
Last edited by jm (2006-10-08 09:31:59)
Offline
Re: Last pre-release: 4.0.4rc1
@michaelpatke, jm: Good point, fixed in svn (will appear in 4.0.4).
@wilshire, ruud: Must have missed that patch, I’ve checked in the fixes now (will apear in 4.0.4).
Offline
Re: Last pre-release: 4.0.4rc1
Some other things. Fixed items are striked through.
forms (see patch sent on september 15th):- <del>‘type’ is required, but you can save with an empty type.</del>
form name should not accept chars like <code>> < " ‘ &</code> because they can’t really be used as attribute values and things get messy in the list of forms on the forms tab if they are used.form name should not be just a series of spaces.on errors (like invalid form name or duplicate form name), it would be nice if the form just submitted was not lost but shown again so errors can be corrected.when saving a form to a name that already exists, nothing gets saved, but it then shows the contents of the already existing form. The form just submitted is lost.
links on the right side of the page tab are not urlencodedsame problem as on the forms tab with <code>> < " ‘ &</code> characters and names that are nothing but spaces.no detection of duplicate names is done.- on errors, the page you just submitted is lost (similar to forms tab)
chmod 644 instead of 755. In one place, chmod 644 is already used, but two other chmods remain.
linebreaks should be stripped from the selectors, properties and values, otherwise they don’t display properly in the input fields when you’re using the CSS editor instead of the raw edit mode.CSS editor has a duplicate ID called ‘edit’same problem as on the forms tab with <code>> < " ‘ &</code> characters and names that are nothing but spaces.no detection of duplicate names is done.- on errors, the style you just submitted is lost (similar to forms tab)
makeOut probably shouldn’t use htmlspecialchars (messy vars and clean vars should be the same)
Last edited by ruud (2006-10-09 23:30:43)
Offline