0.9.5 Bugs and To Dos

I’ve now spent at least 6 hours going through the bug tracker to distill it down to the key To Do items and bug reports. I’ve closed out a lot of bugs where possible, and moved some others to feature requests. I also created a dedicated QuickEdit project to better track those reports and feature requests. Feature Requests would be nice to add, but I did not include them as a list of key things for 0.9.5; view all items under advanced search to see those.

I’ve tried to prioritize the bugs and I’ve assigned many to folks. The assigned bugs are only a suggestion on my part; if you can’t or don’t have time to work on them, please say so here. If you can tackle one or more that you’re not assigned to, please also say so here. Most are not assigned, so any proactive fixes will be more than appreciated.

Many bugs are already completed and just require testing. Some also have suggested fixes listed in the comments. If you think any can be deferred to post 0.9.5 then let’s do so; if you think any should be promoted/demoted in priority, let’s likewise do so.

And let’s get a public beta test out this week!

P.S. as of this exact moment, the trunk will not pass an install... Jared’s diagnosing the issue now and we should have it back alive shortly.

Is that not related to the default content issue Susan raised?

Quote from: PaulGregory at Aug 13, 2006, 06:05 PM

This default pages issue also affects the single "MODx CMS Install Success" page added for people who *don’t* choose the default content, so this makes the current SVN uninstallable as-is.

Add ’’, after ’minimal-base’, on line 741 of setup.sql - and similarly after every alias in the default content.

I had this issue with an install yesterday, did exactly what I said there.

EDIT: Checked, and that’s fixed in the files she uploaded, so presumably it’s something else?

Ryan, you absolutely rock! I’ll go in and start locking down on some of the bugs that have been assigned to me. Hopefully we can knock alot of them out real soon.

Quote from: rthrash at Aug 14, 2006, 09:54 AM

P.S. as of this exact moment, the trunk will not pass an install... Jared’s diagnosing the issue now and we should have it back alive shortly.

I had some problem installing so far but I finally just DLed from public SVN (reading : rev 1265) and it’s working... do I have a different version ?
Anyway, off to testing now !

One thing I could do also is track the language strings to be translated, it nothing (or not much) is expected to change in that area...

Quote from: davidm at Aug 14, 2006, 10:36 AM

One thing I could do also is track the language strings to be translated, it nothing (or not much) is expected to change in that area...

There’s talk of clearing out stuff, and I worked out which old ones can be shifted out... but there’s a number still used by pages that are probably being redone (eg credits) so I felt it best to hang on until nearer the release. I’m still happy to do this, and I believe I’m getting an SVN branch which will make that all much easier.

To the best of my knowledge all the new 0.9.5 lang strings are right at the end and that list could be circulated amongst our international friends.

Paul, you’ve now been assigned some bugs and have your on branch to take care of ’em with.

Quote from: rthrash at Aug 14, 2006, 09:54 AM

P.S. as of this exact moment, the trunk will not pass an install... Jared’s diagnosing the issue now and we should have it back alive shortly.

It’s working. It was a ghost in my machine apparently, not a MODx issue. Although we did discover that having a blank config.inc.php file at install START chucks a wobbly. Normally I don’t create my config.inc.php file until I get to the part of the install where it fails to find it writable, but this once I had it from the getgo. And crash. No joy. Would be curious to know if that’s happening to anyone else before I bug track it. Just create your config.inc.php file THEN point your browser at the root directory.

Quick bugtracker guidelines...

If you finish a bug report, please test to make sure it works as expected locally, then do the following:

• commit the change to your trunk
• mark the bug 100% complete and requires testing as the status
• add a note stating which commit number fixed the bug in the comments

When we’ve got consensus and multiple verification that the bugs are in fact fixed, we’ll close them out. Thanks!