MODx 0.9.7 alpha 2128 (Internal Team Preview)

Intel Mac, latest version of MAMP, no-go.

Same here, not working with latest 1.4.1 also downloaded yesterday, also Mac Intel. Also doesn’t work with PHP5 and works with PHP4...

I didn’t think to mention it, but now that you do, I downloaded the Universal binary version (what about you Mark, did you get Intel or Universal binary ?). There are 3 versions of MAMP : Universal, PPC and Intel and maybe they’re not identically compiled

Quote from: davidm at Dec 22, 2006, 03:32 AM

Same here, not working with latest 1.4.1 also downloaded yesterday, also Mac Intel. Also doesn’t work with PHP5 and works with PHP4...

I didn’t think to mention it, but now that you do, I downloaded the Universal binary version (what about you Mark, did you get Intel or Universal binary ?). There are 3 versions of MAMP : Universal, PPC and Intel and maybe they’re not identically compiled

If you download the universal, you are getting a bigger package that has both intel an PPC executables. Your Intel mac is only going to run the code compiled for intel no matter which download you choose (Universal (larger file) or intel only).

-sD-

Unfortunately I’m going off to Scotland for Christmas, and planning on using the laptop to play music, so I won’t have much chance to really play with this before New Year.. As I type, I’m uploading it to a domain on MediaTemple as that’s a known compatible environment.

Three thoughts:
1) It will be useful to compile (possibly into the first post) a list of hosting environments that are known to work, with notes on the changes required. This would be a bit more positive than just a list of problems!

2) I really hope that this will be up-to-date with the late 0.9.5 changes before 0.9.7 alpha goes public, because otherwise all reports will just be full of people picking up on the changes that are missing and already known. Is it the case that the team can assist with that?

3) If QuickEdit needs to be "refactored", who is going to do that? There’s a lot to be said for just replicating (and extending) the functionality in an all new Thing entirely in MODx front-end code.

I’ve got it working nicely on a HeartInternet reseller’s server; it was an upgrade and I had to insert some values in the database dealing with the sessions and caches that somehow didn’t make it through the upgrade.

I also have it working as a new installation on a MAMP 1.4.1 PPC version, in PHP 5.

Quote from: PaulGregory at Dec 22, 2006, 11:06 AM

1) It will be useful to compile (possibly into the first post) a list of hosting environments that are known to work, with notes on the changes required. This would be a bit more positive than just a list of problems!

Agreed, and definitely part of my motivation in releasing this to the team now, rather than later.

Quote from: PaulGregory at Dec 22, 2006, 11:06 AM

2) I really hope that this will be up-to-date with the late 0.9.5 changes before 0.9.7 alpha goes public, because otherwise all reports will just be full of people picking up on the changes that are missing and already known. Is it the case that the team can assist with that?

It is merged with latest trunk as far as the manager goes. Some of the most recent changes to the manager just need to be verified (merges may have broken some new functionality there) and some of the more recent tweaks to document.parser needs to be re-applied to the new core classes responsible for those features now (i.e. latest updates to TV functionality needs to be migrated to the modTemplateVar class).

Quote from: PaulGregory at Dec 22, 2006, 11:06 AM

3) If QuickEdit needs to be "refactored", who is going to do that? There’s a lot to be said for just replicating (and extending) the functionality in an all new Thing entirely in MODx front-end code.

Hopefully this will be a collaborative effort where I work with someone (Adam?) to make sure we strike a good balance between optimizing the core parsing events and optimizing the QuickEdit plugin. I don’t see any reason to start from scratch. We just need a find a way to resolve the fact that instead of 10 finite passes of the mergeDocumentContent() function being called per document, as well as an equal number of OnParseDocument events being triggered, that we now have a potentially infinite number of passes (with protections for infinite loops by refusing to parse the same tag nested within another and by limiting the maximum parsing iterations in a configurable way) that may or may not be relevant to the needs of QuickEdit. Shouldn’t be that big of a deal, and even with the 60+ passes of QuickEdit, the processing time is not that unusable; just would be nice to get it back to the same performance level of 0.9.5 at least.

Quote from: sottwell at Dec 22, 2006, 11:19 AM

I’ve got it working nicely on a HeartInternet reseller’s server; it was an upgrade and I had to insert some values in the database dealing with the sessions and caches that somehow didn’t make it through the upgrade.

I also have it working as a new installation on a MAMP 1.4.1 PPC version, in PHP 5.

Great news Susan! I found the issue with upgrades (I merged one line in the setup.sql to the wrong place) and will be checking that in soon with some other fixes, adjustments, and new configuration checks. Thank you so much for all your patience and diligent research in trying out this alpha release...

I really want to get a good understanding of how this xPDO core works. I may be working on a major web application next year, and I want it to be based on a very simple framework with a lot of API hooks to hang modules from, and I think your xPDO core will be just the ticket if I can get to the point where I understand it and can do things with it.

Quote from: sottwell at Dec 22, 2006, 11:19 AM

I’ve got it working nicely on a HeartInternet reseller’s server; it was an upgrade and I had to insert some values in the database dealing with the sessions and caches that somehow didn’t make it through the upgrade.

I also have it working as a new installation on a MAMP 1.4.1 PPC version, in PHP 5.

Susan, I think I am going to wipe my install and grab a fresh download of 1.4.1.
Did it work with the standard configuration for you?
Did you change any conf files?
In the preferences, are your ports set to MAMP or to standard?

Thanks in advance.

-sD-

Quote from: sottwell at Dec 22, 2006, 11:38 AM

I really want to get a good understanding of how this xPDO core works. I may be working on a major web application next year, and I want it to be based on a very simple framework with a lot of API hooks to hang modules from, and I think your xPDO core will be just the ticket if I can get to the point where I understand it and can do things with it.

My goal is for everyone on the team to understand xPDO and how it can help them create custom database-driven applications in a lot less time, and with a lot less SQL knowledge. I’m working on some articles, examples, and additional documentation for exactly this purpose. For now, the new modX class (core/xpdo/om/modx095/modx.class.php) is a perfect example of extending xPDO to create a central library for the MODx content management system. Each of the classes in core/xpdo/om/modx095/mysql represent a table in the core database. Each class also has a corresponding map file which describes both DB-specific and PHP meta data that helps automate much of the handling of various data types and describing relationships between various objects. These classes and maps are originally generated from the core/xpdo/_model/modx095.mysql.schema.xml file. Then business logic is added to the classes as appropriate, and that’s about it.

Anyway, start with understanding the xPDO and modX classes first, then start looking at the generated mysql classes/maps. I’ll post some actual working examples of components that make use of the new xPDO features later today...