We have moved to GitHub Issues
Created by Brian Powell 25 Apr 2013, 15:35:39 Updated by Brian Powell 13 May 2013, 14:47:59
Relates to: U4-2209
In 6.0.4, the Umbraco back-end shows pages which had previously been published but are now unpublished as still being published.
If I click the Unpublish button again, the page properties will show as unpublished but if I reload the properties, it'll go back to showing as published. The icon on the tree shows the page as being published the whole time.
This problem, at least the icon status, has crept in since 6.0.3. I'm running MySQL 5.5.24.
I can't reproduce this on SQL, so I suspect a MySQL query issue. Can you delete your logfile then unpublish a page to reproduce this problem and then attach the log file to this issue please?
I attached the log here.
Okay, that gives no clue other than that it's weird that the page "doesn't exist". If you recycle the app pool does the page then look unpublished? Is the page actually gone from umbraco.config? Have you tried unpublishing other pages (and does that have the same behavior)?
Tried recycling the app pool and also doing a full stop/start on the IIS service. No difference.
I'm seeing the same problem with other pages, including when I unpublish pages that were currently published when I did the 6.0.4 upgrade.
The unpublished pages are gone from umbraco.config.
Is the Published true/false value correct in the database if you look in the umbracoNode table? Wondering if its related to the True/False vs 1/0 patch that was committed not to long ago...?
The cmsdocument table correctly shows the page as unpublished.
The true/false vs 1/0 patch was committed before 6.0.3. The status icon displayed properly in that version, but it doesn't now.
I don't remember about the Unpublish button before, but I think the "published but not in cache" error may have been there before 6.0.3.
The patch for U4-2209 (posted there and committed as changeset 6686487bfda6) appears to fix this issue as well.
These two issues appear to have the same root cause of how true/false WHERE clauses for MySQL are generated. Fix crated for U4-2209 seems to have fixed U4-2152 as well.
Backwards Compatible: True
Affected versions: 6.0.4
Due in version: