We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 18654
    • 191 Posts
    I am having a problem with the resource browser (in TinyMCE) where it is not respecting the rb_base_url or rb_base_dir paths in system settings. No matter what values I put in these settings, nothing seems to have any impact on the TinyMCE browser. I am having this same problem locally and on production.

    Local: WAMP 2.0 / W7 / All Browsers 2.1.0 Traditional /
    Production: Bluehost / Linux Server / all browsers 2.1.0 Traditional

    I had the same problem with 2.08pl - I was hoping it would be fixed with 2.1.0.

    I’ve manually emptied my cache numerous times and have tried all different kinds of variations on settings but nothing seems to have any impact.

    See screencast here.

    The resourcebrowser works fine when using it with a static resource - although I still can’t figure out how to get the static-resource-browser to insert an opening slash (i.e. /assets instead of assets) - I hate using base href in my html markup.

    Anyone have any suggestions? Am I missing a setting somewhere or is this a bug?
      God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
      • 28215
      • 4,149 Posts
      From the official docs:


      rb_base_dir

      This setting is deprecated in MODx Revolution. Please use filemanager_path instead.

      You should be using the filemanager_* settings.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 18654
        • 191 Posts
        I deleted my rb_* settings (set to empty string) and tried numerous options to try and get the resource browser to display the right path using filemanager_* settings but nothing seems to work. If my understanding is correct the relevant settings are: filemanager_path and filemanager_url (both _relative options are set to "Yes").

        I have filemanager_path set to /assets/media (also tried /assets/media/) and that works fine for defining the start point for RB and File manager. However, the filemanager_url seems to have no effect on the TinyMCE RB (as mentioned above, RB works fine for Static Resources). Instead of inputting the path /assets/media/images/someimage.jpg it will only input images/someimage.jpg into the path field.

        Any other suggestions? Is this working for everyone else (with file path set to relative path /somedir/somedir)?

          God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
          • 3749
          • 24,544 Posts
          Here are a couple of things to try:

          {base_url}assets/media/images/

          http://yoursite.com/assets/media/images/
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 18654
            • 191 Posts
            Quote from: BobRay at May 25, 2011, 12:38 AM

            Here are a couple of things to try:

            {base_url}assets/media/images/

            http://yoursite.com/assets/media/images/

            I tried inputting both of these into filemanager_url but it seems like the TinyMCE Resource Browser is completely ignoring this field. I also tried toggling filemanager_url_relative, but it seems to ignore this also. Perhaps I’ll try a clean installation of ModX and see if that works.
              God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
              • 28215
              • 4,149 Posts
              Try:

              filemanager_path: assets/media/images/
              filemanager_path_relative: Yes
              filemanager_url: assets/media/images/
              filemanager_url_relative: Yes

              Also ensure your base_path is correct in your core/config/config.inc.php file.
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 18654
                • 191 Posts
                splittingred - still no luck. Here’s a link to an updated screencast showing my latest attempt. Perhaps I missed something?
                  God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
                  • 28215
                  • 4,149 Posts
                  Questions:

                  1) Are you using the latest TinyMCE?
                  2) Is your Path Options set to "docrelative"?

                  I just did a test with 2.1 and TinyMCE using your specific scenario, and it worked as expected. I’m not sure what to tell you.
                    shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                    • 32699 ☆ A M B ☆
                    • 427 Posts
                    Just curious if the files have the right permissions and ownership. In other words is Windows blocking access?
                      Get your copy of MODX Revolution Building the Web Your Way http://www.sanitypress.com/books/modx-revolution-building-the-web-your-way.html

                      Check out my MODX || xPDO resources here: http://www.shawnwilkerson.com
                      • 18654
                      • 191 Posts
                      Quote from: wshawn at May 25, 2011, 08:48 AM

                      Just curious if the files have the right permissions and ownership. In other words is Windows blocking access?

                      Given that the Resource Browser works fine for Static Resources, I don’t think think this is a permissions issue.
                        God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.