Copied to clipboard

Flag this post as spam?

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

  • Thomsen 112 posts 335 karma points
    Mar 25, 2019 @ 19:35

    This document is published but its url cannot be routed


    I keep getting this "error" when creating specific content via the ContentService API in V8. The page is created, flagged as published and all the fields are saved, but I cannot view it since there is not created a url for it - not until I save and publish manually via the backoffice.

    Basically I am doing this:

    var content = cs.CreateAndSave("Underskål", productLine.Id, "product");
    content.SetValue("productNum", product.ProductNum);    

    And I have also tried the cs.Create(...) method with no luck, and I have also tried replacing the Danish character "å" with "aa" in the name above. I have also tried doing this in the SaveAndPublish method with parameters:

    cs.SaveAndPublish(content, "*", -1, false);  

    No luck at all. Any help is appreciated a lot.


    enter image description here

  • Thomsen 112 posts 335 karma points
    Mar 26, 2019 @ 10:31

    A solution that works is to reload the in-memory cache manually. Is there a way to call that button reload functionality from my SurfaceController?

    enter image description here

  • Thomsen 112 posts 335 karma points
    Mar 29, 2019 @ 18:31

    For anyone else struggling with V8 cache child deseases when creating content dynamically, waiting for updated documentation and issues to be sorted out, this (as a side effect) will do the trick for this question:


  • Jonathon Cove 14 posts 87 karma points
    Mar 05, 2020 @ 11:21
    Jonathon Cove

    I found I had to use

  • Richard Hamilton 36 posts 158 karma points
    Jul 29, 2020 @ 09:22
    Richard Hamilton

    Has there been any updates on this as it still seems to be an issue.

  • Thomsen 112 posts 335 karma points
    Aug 26, 2020 @ 00:50

    I found out today, that the parent node of the nodes saying this error had a sibling with the same name (dynamically created via ContentService - so no error message or validation to catch the crime). This was causing that all child nodes could not be routed and given a unique url. Renaming that sibling and rebuilding the indexes fixed it and all "un-routed" pages were instantly baptised with a unique url ...

Please Sign in or register to post replies

Write your reply to: