We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 8830
    • 98 Posts
    Hello,

    I'm trying to create a symlink to an Articles container in a multilingual multicontext environment. It doesn't seem to work.
    Actually the same problem is discussed here, https://forums.modx.com/forums/thread/74252/articles-how-can-i-link-to-a-blog-from-other-contexts , but the (unconfirmed) solution seems overly complicated. Is there a simpler solution for this today?

    /E
      • 8830
      • 98 Posts
      *bump*

      Any ideas what the best way would be to create a "symlink" to a blog (Articles container) from one context to an other?
        • 4172
        • 5,888 Posts
        If you are not too far with your multilingual setup, you may try migxMultiLang, where everything is translated on the same resource.
        No different contexts and different resources needed for multiple languages.
          -------------------------------

          you can buy me a beer, if you like MIGX

          http://webcmsolutions.de/migx.html

          Thanks!
          • 8830
          • 98 Posts
          Thank you for the tip Bruno.
          Unfortunately it's a pretty big site, and it's already made with Babel/Contexts.

          Is there a way to extend Articles to work with symlinks over contexts?
          Or maybe create a getter snippet that fetches the blog posts from the other contexts and Articles container (although I fear problems with urls/contexts/tags/comments...)
            • 41400
            • 11 Posts
            Hi,
            I'm digging in some context-problems, too - did you look at the allow_forward_across_contexts setting? setting this to 'yes' might solve your problem?
            Regards
              • 8830
              • 98 Posts
              Thank you for the tip poseidon.
              Actually I forgot about this setting. But unfortunately it doesn't solve the problem. It's the Articles container that isn't designed to be symlinked I guess. This should be filed as a bug in Articles.