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


  • Christo 23 posts 44 karma points
    Nov 25, 2010 @ 12:22
    Christo
    0

    Document.MakeNew and problem with caching

    Hi guys,

    we experience some caching problems while creating new documents via API. Let me explain the szenario:

    1.we check if a document exists(via LINQ)

    2. if not we wil create the new document via Document.MakeNew and Publish() it and UpdateDocumentCache() as well

     

    when we then check again if the document exists (step 1. ) via LINQ we still receive a false even though the doc is definetly there. so at some point the cache is still active. I'm not quite sure if this is a common API issue or a LINQ issue. Or is there another method to force clearing the cache.

     

    in umbracosttings.config we've set ContinouslyUpdateXmlDiskCache to true btw.

    Any ideas? I appreciate your help

    Thanks

    Christo

     

    PS:we use 4.5.2

     

    Copy Link
  • Eduardo 106 posts 130 karma points
    Nov 25, 2010 @ 12:37
    Eduardo
    0

    Hi Christo,

    I had had the same problem but now is solved:

    Just add this two lines of code into the head section of your pages or masterpage:

    <meta http-equiv="pragma" content="no-cache" />
    <meta http-equiv="Cache-Control" content="no-cache, mustrevalidate" />

    Add to the web.config (under System.Web)

    <caching>
                <cache disableMemoryCollection = "true"  
                  disableExpiration = "false"  
                  privateBytesLimit = "0"  
                  percentagePhysicalMemoryUsedLimit = "20"  
                  privateBytesPollTime = "00:00:05"/>
             </caching>

     

    Hope this helps you too.

    Sincere regards,
    Eduardo Macho

    Copy Link
  • Christo 23 posts 44 karma points
    Nov 25, 2010 @ 15:37
    Christo
    0

    Hi Eduardo,

    thanks for ths suggestion. The thing is - I don't even load a new page as such. I'm adding backend-side a new document and check if its there in the 2nd step(no requests/reload between the step 1 and 2.) and the API sais the new document is missing, but it is there and its published.

    So the Meta-Tags and the web.config are irrelevant in this case I'm afraid

     

    Cheers

     

     

    Copy Link
  • Eduardo 106 posts 130 karma points
    Nov 25, 2010 @ 15:49
    Eduardo
    0

    Hi Christo,

    I made a mistake, that wasn't supposed to be here.

    Regards,
    Eduardo

     

    Copy Link
  • Eduardo 106 posts 130 karma points
    Nov 25, 2010 @ 16:06
    Eduardo
    0

    Hi,

    when we then check again if the document exists (step 1. ) via LINQ we still receive a false even though the doc is definetly there.

    Set ObjectTrackingEnabled property to false to prevent LINQ from caching data

    http://msdn.microsoft.com/es-es/library/system.data.linq.datacontext.objecttrackingenabled.aspx

    Or consider using umbraco SQLHelper DataReader

    IRecordsReader reader = Application.SqlHelper.ExecuteReader(@"");

    I use datareaders.

    The code you are running is ok.

    HTH.

    Sincere regards,
    Eduardo

    Copy Link
  • Manos Gatsios 21 posts 41 karma points
    Jan 26, 2011 @ 19:03
    Manos Gatsios
    0

    Hi Christo,

    Recently I had exactly the same situation as you did and after some testing and debugging I discovered that the Document.Children collection (which is probably what the LINQ call is using) is not updated to reflect any newly added children (via a Document.MakeNew() ).

    Instead of iterating through the list of children, try using the Document.GetChildrenBySearch( parent_id, child_name ) instead.

    Assuming you know the name of the document you are looking for (and most probably you do) then calling this method will have the expected outcome.

    I hope this helps.

    Regards

    Manos

     

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft