Subscribe: RSS
  • Can you file that in the bugtracker susan?
      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github |
    • Done.
        Studying MODX in the desert -
        Tips and Tricks from the MODX Forums and Slack Channels -
        Join the Slack Community -
        • Studying MODX in the desert -
          Tips and Tricks from the MODX Forums and Slack Channels -
          Join the Slack Community -
        • I suspect that this is more pervasive than originally appeared. When attempting to create a new Context Setting for this context it gives an error "Setting not found". I rather imagine that somewhere in all that OOP wonderland is more urlencoded Hebrew utf8 strings being compared against an unencoded string.
            Studying MODX in the desert -
            Tips and Tricks from the MODX Forums and Slack Channels -
            Join the Slack Community -
          • Hi
            I have setup a multilingual web projet in Revo with the following params :
            url :
            context : en

            url :
            context : fr

            My images are located in /assets/images/ .
            In TinyMCE, when I try to insert an image in a document, the url generated is assets/images/myimage.jpg when tiny.path_options is set to "docrelative". When path_options is set to "rootrelative" the generated url is /assets/components/tinymce/assets/images/myimage.jpg.
            What params do I have to change in TinyMCE and/or in the contexts to have /assets/images/myimage.jpg generated ?


            In tinymce.class.php, line 141, we have
            $this->properties['document_base_url'] = $this->config['assetsUrl'];

            where $this->config[’assetsUrl’] is defined by
            $assetsUrl = $this->modx->getOption('tiny.assets_url',$config,$this->modx->getOption('assets_url',null,MODX_ASSETS_URL).'components/tinymce/');

            To solve my problem, I had to change line 141 by
            $this->properties['document_base_url'] = $this->modx->getOption('tiny.document_base_url',$this->properties,'');

            Any feedback on this is appreciated.
            • Hi,

              some advertising for my multilingual plugin based on contexts:

              Babel creates linked documents cross different contexts. So you can easyly navigate through your translations. You can also configure the template variables (TV) you want to «follow» when saving the document in the main context. For example, when you modify the value of a TV in the ’web’ context, modifications will also occur in the other contexts.

              please test it, love or hate it, and comment here:

              • If you’re interesed: I wrote some small tutorials about setting up multilingual websites with MODx with multiple contexts:

                Multilingual Websites with MODx and Babel (domain based)
                SEO Friendly Multilingual Websites with MODx and Babel (folder based)
                  Add-On to easily manage your multilingual sites: Babel
                • I have a client that wants their site to have a Norwegian counterpart. after reading this thread and others, I have decided to try it all out. I moved the site from EVO to REVO and followed the DigitalButter tutorial and then short Babel tutorial. I believe it is going good so far, as i am now seeing the new buttons on top.

                  But I am not sure if I actually understand what all is going on. I’m pretty new to REVO and contexts. I’ve been holding off from Revo until I can find a way to customize the install so that it includes pages, files, chunks, etc. that are part of each site I build.

                  Well, this project came up so I am taking the opportunity to get acquainted with REVO.

                  I guess my question is: Now what? Assuming everything is set up properly, what’s the next step? Do I mirror the ’web’ context over to ’no’ (norwegian), or only the actual pages that are or will be translated; I have a 150 page site but only a handful of the pages are actually going to be translated. Do I only build out those pages on the Norwegian side? Does ModX automatically route browser to the right place? How exactly is that working in the background? How does it know when to serve a translated page. Do I supply a link to it or does it serve pages depending on your location?

                  Let me stop with the questions for now! Thanks in advance for any replies.
                  • Hi SpaceCity,

                    For me most important was to put the BaseUrl correctly in the settings for the specific Media Source (Modx->Tools->Media Sources).

                    If nothing helps you out, you can make a hack to tinyMCE to make image urls relative to the Context in TinyMCE.
                    In /core/components/tinymce/tinymce.class.php i added one line to put the Context base_url in:
                    line 37:
                    if(@$this->context->getOption('tiny.base_url')!='') $this->config["baseUrl"]=$this->context->getOption('tiny.base_url');

                    In your context you can now use a key 'tiny.base_url' to set your Context dependent base_url.

                    In my settings I have the tinyMCE path set to rootrelative.


                    [ed. note: dannygorter last edited this post 5 years, 10 months ago.]