We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 37059
    • 368 Posts
    I have a group of resources, each of which has 3 associated files attached through template variables. Every time I add a new resource, I am obliged to navigate to each one of these files. They’re all in the same folder, but nested down several layers deep in the tree - so, I have to expand (wait) expand (wait) expand (wait) etc. each time. After awhile this gets irritating. I’d like to suggest two possible solutions, if others agree:

    1. If possible, make the file tree behave like the resource tree, remembering which folders should be expanded.
    2. Add the ability to have "shortcuts" in the file tree - commonly used directories that can be reached without manually digging down from the webroot.

      Jason
      • 18373 ☆ A M B ☆
      • 3,141 Posts
      Should’ve posted this in the wishlist folder, or even on bugs.modx.com as feature requests (if it’s not there already) tongue

      I like the idea of shortcuts. I seem to remember the file browser remembering the folder you were last in though..?
        Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

        Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
        • 37059
        • 368 Posts
        You’re right - should have been in the wishlist - sorry. embarrassed I did want to get some feedback before posting a formal feature request, however.

        Weirdly it does remember my location - sometimes. Just not consistently. If it’s supposed to do that all the time, I guess I should make a test case and file a bug?
          Jason
          • 18373 ☆ A M B ☆
          • 3,141 Posts
          The wishlist forum isn’t an official feature request forum as far as I personally am concerned.. "official" requests should go in the bug tracker! smiley

          I’m also not sure of the intended behavior... I could imagine it was intended to start from the root for every different TV (or use, in general). It seems odd that it does "sometimes" though, and a little more detail on when it is and when it aint supposed to work would already be a great difference.
            Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

            Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
            • 37059
            • 368 Posts
            I figured out why it wasn’t working on certain file selects - I had a default value in those selects (an "image not available" image). I don’t seem to be able to get rid of it, either, but that’s another issue smiley
              Jason
              • 19369
              • 1,098 Posts
              Quote from: kenquad at Feb 03, 2011, 02:06 PM

              I have a group of resources, each of which has 3 associated files attached through template variables. Every time I add a new resource, I am obliged to navigate to each one of these files. They’re all in the same folder, but nested down several layers deep in the tree - so, I have to expand (wait) expand (wait) expand (wait) etc. each time.

              1. If possible, make the file tree behave like the resource tree, remembering which folders should be expanded.

              I would be very handy to have a expandable file tree. Usually I rename files before upload, like this: file01, file02, file03, in this way I use the file tree just for the first, then I copy the url and paste in the second and third field and I change the number manually.