Copied to clipboard

Flag this post as spam?

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


  • Nicole 2 posts 22 karma points
    Jan 12, 2011 @ 23:35
    Nicole
    0

    Content Publishing 3 Hours Later

    Hi there,

    I started using Umbraco a few months ago. I was able to save, publish and immediately view content on the site. Then one day, nothing I published was visible. Went through all scenarios, refreshed, tried all browsers, tried different computers at different locations. Same thing. The content will eventually publish hours later. I've also tried every publishing scenario. Save then right click publish. Set to publish at a specific time. Click the save and publish button and every combination therein.

    I have noticed that while I am on Pacific Time, Umbraco is displaying Eastern Time. I double checked my computer clock and Internet clock and evertythiing is fine.

    I sent this issue to my developer who set up and manages the site. When she logs in as me, she's able to publish content right away.

    This is very weird - and very frustrating as I'm not able to see what my pages look like.

    I'm pretty sure it's not a user error - I've been publishing for three months with no problems, and have been using other CMS systems for a long time.

    I'm using Windows 7.

    Any ideas???

    Thanks!

    Nicole

     

  • Sascha Wolter 615 posts 1101 karma points
    Jan 13, 2011 @ 00:08
    Sascha Wolter
    0

    Hi Nicole,

    that is indeed very odd. I've had a similar issue with publishing at a specific time and we later had to find out that the server was 2 hours ahead, simply setting the server time solved the issue. Yet that should not be a problem for publishing directly. As your developer is able to log on to the site as well I take it that it is not running locally on your Windows 7 PC? Can you have a look at the server time anyway?

    I also assume that the backend is working fine as expected, meaning documents appear as published and have the correct content? (By the way, you should always be able to click on the 'preview' button at the top of each node/page to take a look at the page, independently of its status.) That would mean that something is not working okay with the cache. Have you tried the 'Republish entire site' option in the context menu on the root node? That refreshes the umbraco.config xml cache which is the main data source for the frontend.

    Please let me know what you found out.

    Cheers, Sascha

  • Nicole 2 posts 22 karma points
    Jan 13, 2011 @ 00:58
    Nicole
    0

    H Sascha and thank you for your quick response.

    No, it isn't running locally on my PC - and I will talk to my developer and see what time is running on the server

    Yes, the backend is working fine - everything that eventually publishes is correct.

    Yes, I have tried the Republish Entire Site, and same thing.

    But, interesting on the preview. I just checked it out. If I preview a page that I HAVE NOT modified, it previews fine. If I preview a page that I have modified, but has not yeat appeared live on the site, I get an error:

     

    Server Error in '/' Application.

    Object reference not set to an instance of an object.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

    Source Error:

    Line 9:      <h1><%=currentNode.Name.ToString()%></h1>
    Line 10: <%}else{%>
    Line 11: <h1><%=currentNode.Parent.Name.ToString()%></h1>
    Line 12: <%} %>

     

  • Sascha Wolter 615 posts 1101 karma points
    Jan 13, 2011 @ 01:09
    Sascha Wolter
    0

    Hi Nicole,

    that is indeed interesting. My guess is that the code tries to get the current Node object from the cache like

    var currentNode = Node.getCurrentNodeId();

    which is fine, however since the node isn't published the data in the cache won't match and the preview page is a bit different from the rest anyway since it's only temporary. My guess is that a simple check for null in the if clause preceding the above code would suffice, so something like

    if (xxxxx && currentNode != null)

    There might also be trouble ahead with the .Parent reference, so it's a good idea to check for null here as well.

    Thankfully (or not?) I don't think the new problem has anything to do with your initial issue, though I might be wrong.

    Hope that helps,

    Sascha

Please Sign in or register to post replies

Write your reply to:

Draft