MODx 0.9.1 rev 609 (internal testing)

New test build with all the QE-related files (rev 579).

Ok, updated an existing fresh install of rev575 and now the Hide in menu ajax bit works flawlessly (REALLY COOL ADAM!) but the publish option leads me the 404 page but it does unpub the document.

Quote from: Mark at Dec 09, 2005, 10:00 AM

Ok, updated an existing fresh install of rev575 and now the Hide in menu ajax bit works flawlessly (REALLY COOL ADAM!) but the publish option leads me the 404 page but it does unpub the document.

Yes that’s because it’s unpublishing the document and in turn will not let you view so it sends you to a 404. However, there should be a new View Unpublished Documents permission setting that you can set in the role that will allow you to view unpublished documents.

But you can’t edit the administrator role!

There’s something weird gonig on. I’ll test it a bit furter and get back to you.

Okay, I just commited a fix that should take care of giving the view_unpublished permissions to the admin role after an upgrade.

I’m still seeing something very strange on one of the sites I upgraded but not on another. I’m wondering if anybody else is having the same problem

Here’s what’s happening: when viewing a published page and setting it to unpublished via the QE toolbar I get a 404 on the refresh ( javascript:window.location.reload(); ) but if I then type in the URL of the unpublished page I can access it.

Is anyone else having this happen to them?

Ditto! Same problem.

Okay, I’ve got it partially figured out now. There are two problems it seems.

Number one is that I must have miseed getting the code into SVN that is needed to actually allow the viewing of an unpublished document.

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.

Could somebody eles confirm this for me. If it’s not just me then I’ll log it in the bugtracker.

I’m attaching an updated document parser file which will fix the first issue.

Confirmed! Same Problem.

Was the above bug fixed Adam?

Rev 595 attached as the latest test build.