We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 38660
    • 7 Posts
    Hello,
    I just updated Revolution from 2.0 to 2.2.7. Now my Links via [[~x]] are not working anymore. They worked fine under Revo 2.0. I did not change the context-settings (base_url and site_url in both contexts) after the update.
    Any suggestions what could have went wrong?

    Thanks

    panophoto_hh
    [ed. note: panophoto_hh last edited this post 13 years, 6 months ago.]
      • 27708 MODX Staff
      • 2,502 Posts
      Did you clear the site cache after the upgrade?
        Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
        • 38660
        • 7 Posts
        Quote from: smashingred at Apr 20, 2013, 08:15 AM
        Did you clear the site cache after the upgrade?

        Yes, of course. I also cleared the cache manually in the core/cache directory.

        Just as an information: Because I needed a solution I copied the linked files of the other context into the context, where the link comes from, so I don't need to link anymore to another context.
        But I don't think, that's the way modx is supposed to work, so I am still interested in a "real" solution.

        thanks

        panophoto_hh [ed. note: panophoto_hh last edited this post 13 years, 6 months ago.]
          • 10174
          • 15 Posts
          I have the same issue. I solved it by using the path to the folder of the context the link is pointing to, but I prefer to use resource ids.

          Bringing this back in the next update is desired.
          Thanks. [ed. note: friedaweb last edited this post 13 years, 5 months ago.]
            • 9102 ☆ A M B ☆
            • 318 Posts
            I was able to work around this by calling makeUrl in a snippet, see this post: https://forums.modx.com/thread/83913/inter-context-links-disappear-in-upgrade-to-2-2-7#dis-post-466308