MODx 0.9.1 rev 609 (internal testing)

Finally, I got around to getting the latest updates from SVN.  Please test the crud out of this, especially the install.  This is our first impression to people, and I want to make sure we’ve taken care of as many of the already experienced variety of issues as possible before releasing 0.9.1 to the public.

I got rev574 in just a bit too late. The upgrade does not update module configuration variables so if you do an upgrade you’ll need to overwrite your QuickEdit module configuration string with the string from the module comments.

And I missed a few snippets too... rev 575 attached incorporating those changes.

This should not need to be done by the user:

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.

In FF, the new AJAX checkbox’s for Hide in menu and published don’t seem to work in FF.

I looked at the source and every js line ends in ;; instead of ; .

NOTE: The new version of NewsListing has some minor changes to the default template and an all new bit of css styles for the new pagination and archive bits.

This could mean that it will break continuity on designs (NewsListing) for existing installs, but have no effect on functionality. I personally like it better and think it’s not a big deal.

Quote from: Mark at Dec 08, 2005, 11:42 PM

In FF, the new AJAX checkbox’s for Hide in menu and published don’t seem to work in FF.

I looked at the source and every js line ends in ;; instead of ; .

I just fixed the ;;s but that wasn’t really the problem. I just checked some of my code against SVN and found out that certain things were not commited. It seems that SVN doesn’t want to commit anything that isn’t a php file for some strange reason. So the js and css files on svn are out of date. I had a similar problem earlier with image files.

I still can’t get it to commit or even acknowlege the fact that my local code is diffrent from the trunk. Does anybody have any idea what the issue is? I’m using command line svn in linux.

P.S. I’ll see if I can find someone who can do the commit for me in the meantime.

Operator Error.

Send me or Jason the other files and we’ll commit them.

Okay, finally got it figured out. It seems that some .svn dirs from another branch found it’s way into the mix. Should all be fixed now and I just committed the most up-to-date files.