Pre 3.2 release bug testing files

Please run it through the ringer and test against the bugs marked 100% in the bug tracker. Enjoy!

UPDATE:
New file attached below. Please test for hopeful late Monday/Tuesday AM release. Thanks.

Just out of curiosity, is there anyway to generate unified diffs between two versions in SVN?

The reason I ask is that there are some fairly substantial changes between 3.x and what I’m doing, especially since not all files still exist and/or the way certain things work has changed. I’m pretty much positive that attempting to apply these changes to my branch will break a lot of the files I’ve already finished, so it would be easier if I just applied all the changes manually to get caught up...

We’ll need to work that out during the merge. When you SVN Add, SVN Remove etc., that will be applied to the trunk as well, and any conflicts will be handled before any commit is made. It’s really not that bad of a process, even when there are major changes in existing files.

Okay, I have the next version of QuickEdit ready for inclusion in 3.2. I havn’t set up SVN yet so I’ll just post it here. I’m getting pretty tired so if there are any really stupid mistakes you’ll know why.

The big improvements are better API integration, some permissions fixes, integrated documentation (Just run the module) and better custom CSS support. I also did a bit more cleaning up of the code and better error checking/reporting.

The documentation still needs styling. I should have time to work on that tomorrow. Plus I’m sure it needs some serious proofreading.

Give it a try and let me know what you think. I wont be adding any new features for 3.2 I’ll just fix any bugs that may be found before 3.2 is released. Thanks for the help with the testing, and good night

Quote from: OpenGeek at Aug 19, 2005, 11:36 PM

We’ll need to work that out during the merge. When you SVN Add, SVN Remove etc., that will be applied to the trunk as well, and any conflicts will be handled before any commit is made. It’s really not that bad of a process, even when there are major changes in existing files.

Except that authentication, manager/index.php, error handling, messaging, etc., have all been changed. For instance, there is no header.inc.php, footer.inc.php, accesscontrol.inc.php, frames/*, no files with "chunk" or "htmlsnippet", etc., while things like manager/index.php has been completely rewritten, so I’m not exactly sure how its going to merge changes: *Every* backend file has been altered, at least two dozen files removed, and nearly that many more added.

Quote from: infoclipper at Aug 19, 2005, 10:16 PM

Just out of curiosity, is there anyway to generate unified diffs between two versions in SVN?

I think subcommander will do it!

Hi Travis,

Here a copy of the changed files between TP3.1 and TP3.2

I download "Raymond-r241.zip" and install on top of my current Modx installation and go through the install process everything seem to be working just fine.

I have a few questions:
. How do I know I have on the right version?
. Is "MODx 2 TP3 (x2)" a correct version?
. Can we have a consistant convention?
. Is Raymond-r241.zip the right file for TP3.2?
. Can we have a versioning standard like major.minor.fix.dev.a-z?
. Can we use the same standard version number of the page to help to indentify the version of the site?

For example:
The version number would be 0.3.2.a-z or 0.3.2.TP.a-z for version 0.3.2 tech preview a-z
and the zip file would be Modx0.3.2.a-z.zip or Modx0.3.2.TP.a-z.zip

Thanks

. How do I know I have on the right version?
. Is "MODx 2 TP3 (x2)" a correct version?

This version here was pulled in from my SVN branch it’s not the final TP3.2 version. it’s just a test

As it relates to new version numbers I think TP4 will be using such as this is the final release of eto-like version of MODx.

Hmm, I think I prefer the formats:

tp.3.2
beta.1.0
modx.1.0.0
modx.tp.3.2
modx.tp.4.0

Just a thought!

Quote from: xwisdom at Aug 20, 2005, 10:21 PM

Hi Travis,

Here a copy of the changed files between TP3.1 and TP3.2

My hero! Thanks!!