MODx 0.9.7 alpha 2128 (Internal Team Preview)

MODx 0.9.7 alpha (rev 2128)
HELP! I need adventurous testers for this early alpha release of MODx 0.9.7. If you have a few extra moments, give one of the packages below a test run; perhaps do a local test upgrade of a site definition you have laying around, or try out some of your favorite add-ons from the repository or test an indispensable manager feature. I’d like to shoot for a public alpha release for New Years, so please report issues you have as concisely as possible in the topic MODx 0.9.7 alpha 2128 (Known Issues and Suggestions). I’ve included a list of already known issues in the opening post there and will try and keep that up to date.

There’s still a lot of work left to do, and you will likely run into issues with this early alpha, but I was able to complete a new install with the demo content flawlessly today on a mediatemple GS (grid server) account running PHP 4.4.4/MySQL 4.1, as well as PHP 5.1.6/MySQL 4.1 (you can switch this by domain on their service). I also tested it on a local PHP 5.2.0/MySQL 5.0.27 install, where it is performing extremely well BTW. It should work back to PHP 4.3.3 at least, though as usual, I recommend 4.3.11 or higher for a number of reasons, and using PHP 5.1+ with the native PDO mysql driver is optimal¹.

Key New Features
[*] Fully recursive, source-order tag parsing engine
[*] New simplified, yet more powerful tag format, with on-the-fly conversion of legacy MODx tags during parsing
[*] Fully object-oriented API with classes representing every core MODx db table
[*] No eval(); Snippets and Plugins are written to file and included/executed as a native PHP function
[*] Introducing Contexts: these can be used to create isolated sections of your site that override the core system settings; define subdomains or multiple domains within one core, isolate integrated web applications, and much more
[*] Full object and database result-set caching via xPDO to help dramatically reduce database loads and increase scalability for large and/or high-traffic sites

So without further ado, give it a try and see what happens. I’ll be posting a lot more information about this code base as quickly as I can. Feel free to ask many questions...

http://modxcms.com/testbuilds/modx-0.9.7-alpha-2128.zip
http://modxcms.com/testbuilds/modx-0.9.7-alpha-2128.tar.gz

IMPORTANT
¹ -- Make sure if you are running PHP 5.1+ and the PDO extension is configured (it is by default), that the PDO mysql driver is enabled. Some configurations with PDO only have the SQLite driver enabled.

Well, I posted my true thoughts in the known issues thread by accident, but I am infinitely excited about this news.

Thanks OpenGeek,

-sD-
Dr. Scotty Delicious, Scientist.

I was just going to ask you if your branch was usable; I’d checked my email before heading for the forums, and saw your svn update and got quite excited. I’ll load it up on sottwell.com, and we’ll see what breaks, and you can fix it!

By the way, I’m hosted on a system that has php 5 available, but only for files with a .php5 extension. I’d be willing to duplicate my site, one using php 4 and the other using php5.

Quote from: sottwell at Dec 21, 2006, 12:06 AM

By the way, I’m hosted on a system that has php 5 available, but only for files with a .php5 extension. I’d be willing to duplicate my site, one using php 4 and the other using php5.

Certainly would be useful, though I’m not sure how well that would work changing the file extensions. I haven’t focused a lot on PHP 4 testing lately, so doing it with PHP 4 should be a good place to start...

Ok, I’ll stick to 4 then. Changing the file endings would be bad; there are too many places, at least in the Manager, that include or require various files to make it easy.

My local MAMP server is another matter, however. That’s configured to use 5 (not sure at the moment which version).

I just finished backing up sottwell.com, here goes the upgrade!

Quote from: sottwell at Dec 21, 2006, 12:24 AM

Ok, I’ll stick to 4 then. Changing the file endings would be bad; there are too many places, at least in the Manager, that include or require various files to make it easy.

I am not 100% positive, but I am pretty sure that if you are including files through [MODxRoot]/manager/index.php5, then they are, through inclusion, processed as php5.

-sD-
Dr. Scotty Delicious, Scientist.

A clean install on PHP 5 (under MAMP) renders the following error on every page, manager or frontend

Poor Jason, he’s getting hit from all sides here... I already posted that (plus all the problems I had upgrading on my hosted site) on the other topic, http://modxcms.com/forums/index.php/topic,10258.msg70122/topicseen.html#msg70122

I am not 100% positive, but I am pretty sure that if you are including files through [MODxRoot]/manager/index.php5, then they are, through inclusion, processed as php5.

That may be true, but there are way too many places in the manager’s code where the index.php file is specifically referred to. It would take hours to dig through and replace all of those, even with a file editing system that did search/replace across multiple files that’s a chancy thing to do.