Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 11:57
    Sören Deger
    0

    Unpublish Date Bug in Umbraco 6.0.3

    Hi,

    if I set the "Remove at" date today (2013-04-05) to 2013-05-04 00:00 and save or save & publish the node, the node is unpublished!

    Is this an issue in Umbraco 6.0.3? I have tested this in a lot of Umbraco 4.7.+ websites on the same server and it works perfect. Only in all of my Umbraco 6.0.3 websites are the same bug.

    Have anyone a solution for this?

    Best regards

    Sören

    Copy Link
  • Dave Woestenborghs 3504 posts 12135 karma points MVP 9x admin c-trib
    Apr 05, 2013 @ 12:01
    Dave Woestenborghs
    0

    Seems to me like it works as expected. You tell umbraco to remove to unpublish it today. So that's why your node get's unpublished.

    Copy Link
  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 12:06
    Sören Deger
    0

    No, I tell umbraco the date 2013-05-04 00:00 and click on done, not on today and save & publish. After this, the node is unpublished. But the node should go unpublish next month.

    Copy Link
  • Dave Woestenborghs 3504 posts 12135 karma points MVP 9x admin c-trib
    Apr 05, 2013 @ 12:13
    Dave Woestenborghs
    0

    Just tried to reproduce this on a 6.0.3 install and everything seems to work here.

    Could it be that you have a 3rd party package installed that could interfere with the publishing of the node ?

    Copy Link
  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 13:04
    Sören Deger
    0

    I have now install a new empty 6.0.3 without any packages on another webserver. I have created one document type and have created one content Node. I have the same bug. You must reload the nodetree, wait round about 1 Minute and reload the nodetree again: Now the node is unpublished...

    Can you reproduce this now?

    It's only with the "remove at" date 2013-05-04. It seems like the month and days are changed. With another date it seems to work. But in the sql-database the expireddate is saved in the correct format.

    Copy Link
  • Dave Woestenborghs 3504 posts 12135 karma points MVP 9x admin c-trib
    Apr 05, 2013 @ 13:24
    Dave Woestenborghs
    0

    I can not reproduce it.

    Did you make some culture changes in you web.config perhaps ?

    Copy Link
  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 13:36
    Sören Deger
    0

    No, I have nothing changes in web.config. But my SQL-Server has german language.

    Copy Link
  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 13:38
    Sören Deger
    0

    Seems to be a date formating issue. 2013-05-04 means the 4th of May, but maybe, it is interpreted as 5th of April, this would explain the behavior. YYYY-MM-DD <> YYYY-DD-MM.

    This may be caused by the German language? May perhaps anyone else reproduce the error?

    Copy Link
  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 13:42
    Sören Deger
    0

    I have now tested this on 4 independent servers. Everywhere I have the same error, but only in 6.0.3. In all of my 4.7+ websites on this servers it works perfect.

    Copy Link
  • Dave Woestenborghs 3504 posts 12135 karma points MVP 9x admin c-trib
    Apr 05, 2013 @ 13:46
    Dave Woestenborghs
    0

    I think you found a unknow bug. Best to create a issue for it on http://issues.umbraco.org

    Copy Link
  • Dave Woestenborghs 3504 posts 12135 karma points MVP 9x admin c-trib
    Apr 05, 2013 @ 13:49
    Dave Woestenborghs
    0

    Maybe a quick workaround be is to set your culture in the web.config ?

    Copy Link
  • Sören Deger 733 posts 2844 karma points c-trib
    Apr 05, 2013 @ 13:59
    Sören Deger
    0

    Thank you, I have create an issue.

    Copy Link
  • Ian Smedley 97 posts 192 karma points
    Jul 11, 2013 @ 12:01
    Ian Smedley
    0

    I am also experiencing the issue on 6.1.1 - ~ I have updated the issue log with some comments, and voted it up.

    http://issues.umbraco.org/issue/U4-2055

    I also found this issue - which has alot of votes - perhaps it could be related?

    http://issues.umbraco.org/issue/U4-2055

     

    Copy Link
  • SC Digital Services Team 104 posts 171 karma points
    Apr 08, 2014 @ 13:37
    SC Digital Services Team
    0

    Looks like this bug has resurfaced - we've got the same issue with fresh instances of 6.1.6: http://issues.umbraco.org/issue/U4-4401

    Copy Link

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies