We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14930
    • 70 Posts
    Thanks, sinbad, but that didn’t work either.
      • 14930
      • 70 Posts
      I’ve done a bit more experimenting now, still the problem persists.

      It seems that the "Resource path" and "Resource URL" don’t do anything, it doesn’t matter what the content is, the links to the displayed files still stay in the same format: http://sitename.net/www09/manager/..%2Fassets%2Ffiles%2Fextra%2Ffilename.doc

      As you can see the "/manager/.." part should’nt be there.

      Only changing the "File Manager path" seems to work as intended.

      Any ideas why? I’ve tried changing both the user configuration and the system configuration, but no luck.

      Could this have something to do with friendly URLs?

      One more strange thing: I can delete the files just fine from File Manager, just the "Download file" button (floppy disk image) link is wrong.

      EDIT: I’ve also tried putting files to another directory and changing the permissions.
        • 26627
        • 1 Posts
        Did you find a solution to this? I am experiencing the same thing. It seems like it is going to the right path, the best I can figure is that the url encoding is messing it up. Any help is appreciated.

        Thanks!
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          Resource Path and Resource URL are only for the Rich Text resource browser (the images button in the toolbar of TinyMCE).
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 14930
            • 70 Posts
            Quote from: semiplay at Jun 03, 2009, 07:41 PM

            Did you find a solution to this? I am experiencing the same thing. It seems like it is going to the right path, the best I can figure is that the url encoding is messing it up. Any help is appreciated.

            Thanks!

            Sorry, I didn’t. The client is using ftp to manage his files. I have no clue.
              • 27330
              • 884 Posts
              what is the host you using?
              that might bring someone who host with them too to share his working config.
                • 14930
                • 70 Posts
                I upgraded the install, but the problem still persists.
                The host is domainkeskus.
                  • 14930
                  • 70 Posts
                  Okay, I tried a new install in a subdirectory, the same error still persists. Changing the Resource URL seems to have no effect. I’ll inform the host about the problem but I think I’ve got to change hosts next.
                    • 28042 ☆ A M B ☆
                    • 24,524 Posts
                    The Resource URL (in the Interface and Features tab) is only for the resource browsers in TinyMCE. For the Manager’s file manager you need to have the right path in the File Manager tab.

                    If you can see the files then the path is correct. Not being able to download files from the File Manager is something else. It looks like the calculations for determining the path to use when creating the download links are not working correctly. I’ve run across servers that return odd stuff in the SERVER array causing MODx’s calculations to fail; it all depends on the server configuration.
                      Studying MODX in the desert - http://sottwell.com
                      Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                      Join the Slack Community - http://modx.org
                      • 14930
                      • 70 Posts
                      Hmm. Just to see if it was server-related, I installed MODx (0.9.6.3, rev 4565) to this other server (that I use for my personal projects) and I still get the same thing straight after installation.

                      Then I tried it with yet another server (the same MODx version), and yeah, the same error comes up again. So apparently even switching servers wouldn’t help, this is clearly a bug in MODx 0.9.6.3? Or the configurations or something are messed up straight at new install.

                      The database versions are 5.0.26-standard-log, 5.0.21-log and 4.1.20, so I don’t think it’s a MySQL incompatibility issue either.

                      Any ideas? Seems like I’ll be updating to 1.0.0..