Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Help us test release candidate 2 (!) for the upcoming 4.0.8 release
The final, official 4.0.8 release is scheduled for mid-January 2009, unless unexpected problems or errors arise.
We’re looking for people who like to help us make sure that we didn’t miss any regressions or introduce new bugs. We would like to get feedback on clean installations and updates from older versions.
Make sure that if you use this release candidate, you also update to the final 4.0.8 version when it is released.
Download
Notes
The included HISTORY.txt file already lists most of the important changes since 4.0.7. If we missed something, let us know.
The download advertises itself as 4.0.7 (r3074) in diagnostics, because we haven’t yet bumped the version number.
Edit: Modified for RC2.
Last edited by wet (2009-01-16 20:46:12)
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Be glad to test, and for the sake of others reading this thread, here are the changes listed in history.txt:
Changes in 4.0.8
* Fixed: Current section/category is overwritten in <txp:section_list> and <txp:category_list> (container or form mode)
* Fixed: Registration and notification mails are not sent in PHP safe mode.
* Fixed: Error message upon article save from MySQL 5 in 'strict' mode.
* Changed tag: <txp:if_section> without a name attribute is now TRUE on a section page (old behaviour is preserved on upgrades).
* Changed tag: <txp:if_category name=""> is now FALSE on a category page (old behaviour is preserved on upgrades).
* Speed: faster plugin loading from the database.
* Diagnostics tab: ignore line endings when checking for modified files and show full paths.
* Pages tab: allow 'default' page to be deleted if not used by a section.
* Developer: Fall back to standard page/permlink behaviour if custom_url_func() returns FALSE.Last edited by jstubbs (2008-12-27 21:22:52)
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Changes in 4.0.8
* Fixed: Current section/category is overwritten in <txp:section_list> and <txp:category_list> (container or form mode)Does this mean the behaviour outlined in this post will be adopted in 4.08?
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Yes, but these two lines indicate said change:
* Changed tag: <txp:if_section> without a name attribute is now TRUE on a section page (old behaviour is preserved on upgrades).
* Changed tag: <txp:if_category name=""> is now FALSE on a category page (old behaviour is preserved on upgrades).Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
OK – thought you wanted to wait on that. I’ll test it out tomorrow. Thanks for the updating 4.07 so fast!
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
This is great news and I’ll give it a shot on my development server.
Does this mean the team is trying to move towards smaller but more frequent version updates?
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
No. This is just to fix a few very annoying bugs in 4.0.7.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
“txp_diag” seems to be working nicely now. I’m not getting an annoyingly long list of “modified files” even though I’m using the development version. :)
Stuart
In a Time of Universal Deceit
Telling the Truth is Revolutionary.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
thebombsite wrote:
“txp_diag” seems to be working nicely now. I’m not getting an annoyingly long list of “modified files” even though I’m using the development version. :)
Same here… No visible problems at first glance.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
I’m taking the low number of responses as a positive sign. Nevertheless, if you feel a slight tendency towards testing the release candidate but haven’t yet found the energy to do so: Surrender to your desires and check it out!
Mind you: We will revert to our usual update frequency after 4.0.81, so if there are any hidden bugs they should rather be discovered now.
—
1 ftxp ≈ fwp / 32
2 Sorry for the math, but I’m a communications engineer by education.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
well having said what I said earlier I’m just wondering if it will actually be better if the “modified files” list does appear in the diagnostics.
Although I initially agreed with Stuart, on retrospect I think that having the list provides us with 2 advantages.
- A reminder of what files we modified for our sites’ specific installs
- Quickly check diagnostics posted in this forum.
Having said this, the decision lies with the devs.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Modified files do appear if they are modified. We are just shipping a proper checksum file even for the RC now, which wasn’t the case with previous RCs so those overzealously nagged about modifications.
Offline