We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 21872
    • 95 Posts
    I might be missing something obvious, is there a simple way to restrict the location revealed in the browser to a specific directory? Is this something I can set as a property?

    Thanks.
      • 22019
      • 390 Posts
        Writer > E-consultant > MODx developer || Salesforce || modx 2.x || PHP 5.2.13 || MySQL client 5.0.86
        • 21872
        • 95 Posts
        Thanks, but that seems to be a global setting. Let’s say I have a TV called "header images" and a directory in images called "headers", I want to restrict the filemanager, when used with the header images TV, to the headers directory.
          • 28215
          • 4,149 Posts
          That’s not currently a feature yet; we’re looking into ways of adding ’properties’ to input TV renders (such as image) that will allow for customization per-TV of inputs, but that wont happen until 2.2, most likely.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 21872
            • 95 Posts
            Sounds excellent, I’m continually impressed by the thought and attention to detail that goes into each release. Thank you for making such a fantastic platform available.
              • 10313
              • 375 Posts
              Quote from: odeclas at Dec 22, 2010, 03:42 AM

              filemanager_path http://rtfm.modx.com/display/revolution20/filemanager_path
              If I set filemanager_path to "assets", the file browser starts in that directory. After selecting an image, I can see the preview, but in the text field, the "assets"-part is missing. This is the same for TVs and for TinyMCE (while TinyMCE does not show the preview). In the front end, the images do not show (because of the missing "assets/").

              What do have I have to do?