We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32678
    • 290 Posts
    I have:

    • FURLs enabled
    • Friendly alias path set to 'no'
    • Published resources nested within an unpublished container
    • manually cleared system cache, and cleared browser cache

    What I get is mySite.com/unpublished container/nested-resource.html. Shouldn't this result in a flat URL when navigating to 'nested-resource.html'?

    Freezing every nested resource URI is not a viable option.

    What I really need is the ability manage directory paths in a straightforward manner. I need to show some while hiding others.
      • 10208 ☆ A M B ☆
      • 1,780 Posts
      I think you're going to get the path from the tree whatever you do.

      What about using First Child Redirect and publishing the container (give it a decent pagetitle/alias), but not allowing actual access to the container? http://rtfm.modx.com/extras/revo/firstchildredirect
        Frogabog- MODX Websites in Portland Oregon
        "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
        Having server issues? These guys have MODX Hosting perfected - SkyToaster
        • 32678
        • 290 Posts
        Quote from: frogabog at Feb 13, 2015, 04:03 AM
        I think you're going to get the path from the tree whatever you do.

        Why have a friendly alias path setting at all then? Its wording is specific -- "setting this option to 'yes' will display the full path...". The implication is that if you don't set it, you don't get a full path.

        Quote from: frogabog at Feb 13, 2015, 04:03 AM
        What about using First Child Redirect and publishing the container (give it a decent pagetitle/alias), but not allowing actual access to the container? http://rtfm.modx.com/extras/revo/firstchildredirect

        Thanks for the suggestion. In my case, the nested resources are accessed from gallery pages that are in a different part of the site tree. The resource thumbs are fed via tags and getResources into the galleries, and because tags are used a single resource can appear in multiple galleries (i.e. I avoid duplication).