We have moved to GitHub Issues
Created by Sebastiaan Janssen 19 Aug 2012, 14:52:29 Updated by Sebastiaan Janssen 31 Jan 2013, 16:05:59
Is duplicated by: U4-331
Is duplicated by: U4-848
Relates to: U4-278
Subtask of: U4-760
Sometimes if publish a page, the tree in the node shows the unpublished icon. See attachment. I'm using Umbraco 4.7.
''Originally created on CodePlex by [jbreuer|http://www.codeplex.com/site/users/view/jbreuer]'' on 4/11/2011 3:18:24 PM [Codeplex ID: 30241 - Codeplex Votes: 5]
''Comment by [sebastiaan|http://www.codeplex.com/site/users/view/sebastiaan] on 8/9/2012 11:48:56 AM:'' We haven't been very good at maintaining the issue tracker and with 1250+ open bugs we can't be sure which ones have been fixed and when (if they are even fixed).
To keep the issue list maintainable, on Monday the 13th of August, we will be moving the issue tracker over to YouTrack (http://issues.umbraco.org) where we'll only import the issues that have been updated in the past 12 months (which means: they had comments or votes in the past year).
If you think this issue (that has had no activity in the past year) is still worth looking at then please comment and we'll look into re-opening it.
''Comment by [sebastiaan|http://www.codeplex.com/site/users/view/sebastiaan] on 8/15/2012 3:10:22 AM:''
May be that the SQL Server date/time is not matching the system date/time. UpdateDate is set with DateTime.Now in code and cmsContentVersion.VersionDate is set by the database with a default value. Of course, load-balanced servers could result in the same issue.
Either all dates need set by the db or by the application, not both..
Seems that these issues are related, but unfortunately Casey, I can reproduce this in a small local environment (SQL CE), no datetime differences, no load balancing.
Corrected in changeset: a248c20804ba The original code was moved from the tree to the document. When this happened, the time comparison changed from rounded seconds to milliseconds. rounded seconds > 1 = milliseconds > 1500. I changed and pushed it at 2000 milliseconds.
After having Jan test the fix, it turns out 2000ms isn't enough even.. looking at the code comment I am not sure I completely get what this is doing either (umbraco.cms.businesslogic.web.HasPendingChanges()):
So it's saving, then looking at the datetime in the db to see if there are more changes? I had to set it to 5 seconds for it to work properly for Jan (Windows Experience Index: 5.1, so a normal HDD, non-SSD and +/- 2 year old processor). That's probably even better than what most editors are using, so I think we need to completely rethink how we're checking this.
Yea, Have Jan compare the db server time with the server running the site.. Bet they are out of sync by a bit. Changing the CreateNewVersion method on the content.cs to use DateTime.Now may help alleviate this issue.
He's using SQL CE, so the time can't be the issue. Also, why is this suddenly a reproducible issue? I've not seen this issue before and the code seems to have been in place for at least 2 years now..
Definitely interesting. Any changes to the SQL Ce scripts? Tree Scripts (I know the methods used to set the styles is listed as deprecated.)
It may be that the save is just taking that long in SQL CE. How big is the document type, and what is the lapse time from submit to response?
I have a similar problem:
Some icon mix-up?
This issue can be reproduced when using SQL Server 2008 R2. I started noticing the issue in 4.8.x. Also, it seems to occur more frequently when more complex datatypes are included in the document type - DAMP, MNTP ... etc.
Rusty's problem applies to me too. I use SQL Server 2008, and this problem always occurs on doctypes with MNTP datatypes.
Unfortunately we cannot reliably fix this before 4.9.0 is released so we're moving this to the next sprint, sorry for the delay.
had this problem in 4.8.1, but not anymore after upgrade to 4.9.0
I am seeing this on only sites that are upgraded to either 4.8.1 or 4.9.0. Both sites I have seen this on the DB and IIS are on the same server. SQL 2008 R2 and IIS 7.5. Anyone found a workaround yet?
Just noticed this today running 4.9 everything appears with the unpublished star next to it. Items which are unpublished appear greyed out thankfully so can still see what is what. Reloading nodes/parent node does not flush it.
I've just installed a new 4.9 empty solution, and this happens to me to. Is there a fix for the problem, or should I create a 4.8 solution instead. It's a bit hard to explain to the customers that it is a bug and not a feature...
Now the problem don't exist on a different computer, and after a complete IIS reset and configuration, it now works...
occurs on both 4.8 upgraded to 4.9 and another new 4.9 install. localhost and production server. database - SQL SERVER 10.50.2500
My problem was I had the database on another server, while working locally. I recently moved the site to the same server as the database, and the icons are now behaving as they should.
Before 4.9, though, I never had any of these problems while working locally.
We're experiencing this issue too, 4.9.0
Same here 4.9
This is happening to me on a fresh 4.9 install with a MySql backend.
This just occurred on a 4.9.0 (DB is MySQL) for me - the solution has been running for a couple of weeks without this, but today I used the Publish option in the context menu for the first time (checking both checkboxes) and got the icon overlay on the node+descendants. All subsequent "Save and Publish" actions now result in icons being overlaid on the published node + its descendants...
As a fix we've set the time sync interval to every hour on our servers via a registry file.
@Stefan, how does your script work? What is it doing to fix the issue?
I've got clients asking arkward questions about this one, making us look a little silly. Is there not a patch we could have?
@Pete, it changes the Windows time sync interval from once a week to every hour. This helps to keep the time between the SQL server and the Web server in sync.
There's no patch available yet. However Niels mentioned on Twitter a fix will be included in v4.10.0 which will be released next Friday: https://twitter.com/umbraco/statuses/253424878986866688
I've fixed it (thanks to the awesome debugging info from Kraftvaerk.net and comments in this thread - h5yr!)
I'll push it one of the coming days as it's a part of a bigger changeset with the doctype enhancements which I'll need to merge with 4.10!
For those interested: The issue was caused by two things:
In the fix, the date is stored in a local variable and then passed to the helper method that generates the new version, ensuring that there's no (0 ms) time difference between the version date and the initial update date when a new version of a doc is created. The reason to increase the overlay tolerance time to 2000 ms is to help with those versions / installations already affected.
This problem just went away completely on my installation - does that imply that someone republished everything on a "good day", server performance wise?
If you're running on 4.9.0 without any core modifications, this updated cms.dll should help with your icon problems. This fix is of course included in 4.10.0.
If anybody wants to inspect the code changes, attached is also a patch file which you can ignore if you're not interested in the underlying code.
I'm encountering this bug on v4.9 too. I just uploaded the new cms file from Sebastiaan's comment above and it still isn't resolving the issue.
Brilliant, thanks for fixing this. I just replaced the .dll and it works great!
Sebastiaan, we are on 4.7 and cannot upgrade at the moment, is there a way for us to bump the overlay tolerance to 2000ms as you suggest? We're seeing differences of about 6-700 ms so this might work for us.
@Steve look at the patch file, it shows you the differences in the code from which you should be able to do a custom 4.7 build. Unfortunately we can't provide custom builds for each version of Umbraco that would eat up all of our precious time.
Thank you Sebastiaan, I did not expect you to provide a custom build, I was hoping you knew of a config setting or similar. I am looking into upgrading to 4.10 and I am going to pull down the source for future reference. Thank you for your work!
@Steve Nope, unfortunately the only way to solve this is by updating the code.
Backwards Compatible: True
Affected versions: 4.10.0
Due in version: 4.9.1