MODx 0.9.1 rev 609 (internal testing)

No it never was, at least not by me.

I’ve got some time to work on MODx tonight so I’m going to test Scriptaculous 1.5 and I’ll look into this too. It’s probably a simple fix.

Quote from: aNoble at Dec 09, 2005, 10:54 PM

Second problem is that unpublishing a cached docement doesn’t seem to get rid of the cached file even with clear cache checked. The same thing happens in QuickEdit and the manager. It’s not a huge issue because the fact that the database is being updated with the unpublished flag means it won’t show up in menus or searches but any link directly to the page will continue to work.

Okay, think I’ve got this fixed. Here’s my comments from the commit.

Added document published check before postProcess caching. Previously, all unpublished page requests were redirected to an error page, never generated and never cached. Also requests for cached pages are never checked for pubished status since as unpublished page couldn’t be cached. With the introduction of the view_unpublished permission unpublished pages could be vieved and therfore cached. This update should solve that issue by never allowing an unpublished page to be cached.

Script.aculo.us 1.5 seems to work very nicely so far (havn’t had a chance to check in IE yet, tomorrow). It fixed a bug in Opera and is a lot quicker than the last version. Unfortunately the quickness of it brings out a sort of a "bounce" effect that will hae to be dealt with in some way. I’ve already worked on putting some nice prototype.js featuers I never knew about to use which should simplify and improve things a good bit, I should be able to have all of it working well soon.

Is this all we’re wating on for 0.9.1? If so I’ll definitely make it a priority.

Yep... just you and some more torture in general of the build.

Here’s build 600, including all the latest goodies including the release versions of scriptaculous/prototype. Please beat this one up as it is pretty much one of the last "release candidates" for 0.9.1 (all To Dos and Bugs have been cleared from the bugtracker with this).

Beating up sire!

That evil flicker for QE is back!

UPDATE: QE is practically IMPOSSIBLE to use in IE and annoying in FF.

I installed rev 600, and noticed that on a clean install, some chuncks/snippets have status "Installed", others have "Upgraded".

Nothing to really worry about, but thought, let you know ;-)

Remon

yea, ignore QE in this rev. I’m working on getting it working with scriptaculous 1.5 but I’m not there yet and none of my 1.5 changes are in this release. Hopefully by tonight I’ll have QE working with 1.5.

with the minimal install, all the chunks/snippets have status: installed.

Just to let you know ;-)