MODx 0.9.1 Release Candidate 1 (for internal testing only)

Attached in .zip and tar.gz formats. Have at it team; and let us know what you find via the bug tracker. Remember to search before you submit a new one. And if you happen to know the fix, feel free to submit it along with the bug in the tracker so we can get it into the release.

Lots of core improvements in this one; performance should increase a bit with this release.

Also, please note you can change line 108 of /index.php in the installation from:

to

if you want the parser to stop and report any PHP notices as it encounters them. Great for double-checking your snippet code before releasing it.

[NOTE: Sorry about the name tattoo on the packages -- I meant to put MODx ]

Installing....

Should not need to manually do this!

For new Linux/Unix installs, please create a blank file named config.inc.php in the manager/includes/ directory with file permissions set to 777.

The default snippets need to be updated to the newest versions.

Need to update version #

Default install:

My MODx Site - MODx 0.9.0 (x9)

Manage resources is all messed up...

Tabs don’t appear....

Parse error: parse error, unexpected ’<’ in /home/httpd/vhosts/modxdev.net/subdomains/testing/httpdocs/manager/actions/dynamic/mutate_settings.dynamic.action.php on line 653

On the system settings page....

Right click context menu and document tree heading are missing styling...

I confirm all reported bugs by Mark that they exist...

Moreover manager styles are extremely broken !

regards,

zi

Ok, ignore the manager style problems. I forgot to revert some changes made to the trunk inadvertantly. I’ll get another release out later today to address this. Thanks for the quick feedback, and please continue to post any observations on this test build here in this forum, though new topics are fine if they reference 0.9.1 RC1 and deserve a focused topic to themselves.

Focus some intense testing on the parser in the front-end. We’ve made some significant updates to the parser and want to make sure everything is working as expected in this area. Test as many snippets as possible, upgrades to legacy installations, and if you get the chance, thoroughly test all your snippets with the stopOnNotice=true option. I’ve made a lot of small changes to the core and the default snippets to resolve PHP notices that were previously ignored, but there are many more to go. None of these are show stoppers, as stopOnNotice=false will not reveal these warnings, but code that does not produce these notices is obviously more efficient, as well as a good example to the community.

One last note as a reminder: we’ve been having lots of installation problems with various configurations and versions of MySQL, especially in non-English locales. If you experience any installation problems with this release candidate, please report the complete details in a new topic here in this private forum, unless you are certain the issue has been resolved in this build [EXCEPTION: the latest unconfirmed resolutions to various setup.sql issues is not in this release yet; I’m still trying to get a complete picture of all the issues and the actual resolutions that addressed them]. I’d love to have all of these install quirks worked out for the 0.9.1 release, and every bit of information helps.

Keep up the great work!

Jason,

I think we might want to check into removing the comments on some of the columns. I think that resolved it for some folks. That thing is a total mystery. :/