We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28215
    • 4,149 Posts
    Did you set filemanager_url to assets/files/? You should normally have the _url match the _path.
      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
      • 18463
      • 121 Posts
      Martijn van Turnhout Reply #12, 15 years, 5 months ago
      I did, and it goes totally wrong.

      This is the result of not setting filemanager_path or filemanager_url

      <img src="/assets/components/phpthumbof/cache/assets_files_afbeeldingen_cabinw9.png.e47c45f1d22b7c05a4437b0617da3c41.png" width="160" height="98">
      


      It works fine that way. But this is the result of setting filemanager_path & filemanager_url both to assets/files/

      <img src="assets/files/assets/files/afbeeldingen/cabinw9.png" width="160" height="98">
      


      I’m using phpthumbof and it seems to disregard that plugin?

      I’ve reported this before, by the way. See http://bugs.modx.com/issues/4208. However, my note #12 turned out to be wrong afterwards. That solution seemed to work fine for Image and File TVs which were already present at that time. However, new Image and File TVs suffered the same problem: no "assets/files/" were automatically added in the front-end.

        • 28215
        • 4,149 Posts
        What renders when you put *only* this in your Resource content:

        [[!*cabin_image]]


        ...in the following 2 scenarios:

        1) filemanager_path == assets/files/ - filemanager_url == [blank]
        2) filemanager_path == assets/files/ - filemanager_url == assets/files/
          shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
          • 18463
          • 121 Posts
          Martijn van Turnhout Reply #14, 15 years, 5 months ago
          Shaun,

          I got it! I know what’s causing it!

          I’ve changed both filemanager_path and filemanager_url to assets/files/. Now, when I’m using an Image TV and a File TV for new data, the links all work fine. It’s just that the output URLs of those TVs which were already present before I changed those filemanager settings, aren’t changed automatically afterwards! They still contain faulty links. That’s the thing.

          So it works all fine, but I assumed that all output URLs (in past and future) would change automatically whenever I would touch those filemanager settings. Is that a bug by the way?
            • 28215
            • 4,149 Posts
            Quote from: Martijn at Apr 08, 2011, 09:53 AM

            So it works all fine, but I assumed that all output URLs (in past and future) would change automatically whenever I would touch those filemanager settings. Is that a bug by the way?

            Not really; if you’re going around changing settings for TV paths, there’s no real way for TVs to *auto-fix* the old paths to the new one. 2.1 tries to address this better by storing relative paths, and letting the full path be built out by the TV Input Options/filemanager_path settings. There’s also a bit of backwards compat in the 2.1 tvs to address stuff like this.

            Best principle, though: get your TV settings setup correct before you start putting data in them.
              shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
              • 18463
              • 121 Posts
              Martijn van Turnhout Reply #16, 15 years, 5 months ago
              Thanks for the input. Much appreciated! I think things like these should be documented somewhere. It would help people a lot and take away their confusion.