We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31955
    • 84 Posts
    hi,

    I have 2 (possibly related?) problems regarding image previews: one in the MCPUK browser, the other one in resources -> File manager. I never see image previews, but just broken image symbols instead. I’m not quite sure anymore if it worked under 0.9.6.2, though.

    here some URLs of image locations (i replaced my real domain with MYDOMAIN.COM. The image I chose is the modx-logo that comes with the installation, IIRC)


    resources->filemanager (broken image - other files, like the content of php-files, are shown correctly though)
    http://www.MYDOMAIN.COM/manager/..%2Fassets%2Fimages%2Flogo.png

    edit: solved, see: http://modxcms.com/forums/index.php/topic,32182.msg195648.html#msg195648

    resource browser (broken image icon):
    http://www.MYDOMAIN.COM/manager/media/browser/mcpuk/connectors/php/connector.php?Command=Thumbnail&Type=images&CurrentFolder=/&FileName=logo.png&ExtraParams=

    after selecting that broken image, it is shown correctly in the preview window with its correct location:
    resource browser, after selection (works)
    http://www.MYDOMAIN.COM/assets/images/logo.png

    some of my config:
    manager->site config->resource path: (after 0.9.6.3.-upgrade, i took that path from filemanager-path that was inserted automatically during 0.9.6.2.-setup, and added "assets" to it)
    /srv/www/vhosts/MYDOMAIN/htdocs/assets/

    manager->site config->resource-URL: (I added a starting / to it after upgrading to 0.9.6.3)
    /assets/


    I searched the forum, did find some old info related to mcpuk which doesn’t really fit with my problem, and some other topic mentioning lacking GD-support. phpinfo tells me that gd-support is enabled on my server.

    anyone having a clue?

    edit: Second issue also solved: my MODx’s config.inc.php started Byte-Order-Mark, was encoded in "UTF-8 with signature" - that config file is also loaded by the MCPUK-connector.php, and these 3 bytes were passed through to the output of the preview-image, which was broken as a result. See page 3 here.
      • 23299
      • 1,161 Posts
      AFAIK, the image files that support your site will go here:
      /assets/templates/template_name/images/image_name.png

      I FTP all my site images to this folder. I then point all my CSS images to this folder as well. Some of the gallery snippets like Maxigallery will use their own Gallery folder within the snippet folder to manage the photos via the MODX manager.
        • 31955
        • 84 Posts
        i fear the problem must be something else.
        • See the sticky topic in this board: http://modxcms.com/forums/index.php/topic,31771.0.html
            • 31955
            • 84 Posts
            Quote from: OpenGeek at Jan 05, 2009, 04:28 PM

            See the sticky topic in this board: http://modxcms.com/forums/index.php/topic,31771.0.html

            I read that topic before posting, and read it again right now - if I understand it correctly, the settings I reported above are the settings recommended in that topic.

            still no previews (the MCPUK-browser works in general, but doesn’t preview the images until one is chosen).

            and do you know if the other issue (resources->filemanager not showing image-previews due to special characters in the path) is related or actually a separate problem?
              • 7231
              • 4,205 Posts
              manager->site config->resource-URL: (I added a starting / to it after upgrading to 0.9.6.3)
              /assets/
              I think that this does not need the starting /. Try with only
              assets/
                [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

                Something is happening here, but you don't know what it is.
                Do you, Mr. Jones? - [bob dylan]
                • 31955
                • 84 Posts
                Quote from: dev_cw at Jan 06, 2009, 11:10 AM

                I think that this does not need the starting /.

                no, when I remove that starting /, and click on "edit image" in the mcpuk-browser (while I still don’t see a preview), I get a broken image symbol in the image editor. WITH the starting /, I don’t see a preview, BUT I can edit the image and actually see it correctly.
                  • 31955
                  • 84 Posts
                  see also this thread http://modxcms.com/forums/index.php/topic,32182.0.html
                  wich likely deals with one of the issues I mentioned here.

                    • 17340
                    • 70 Posts
                    Following the leads in this topic we were able to fix one of the problems, i.e. the Resource path URL one and we worked out an internal instruction for this, so people installing 9.6.3 at least could find it in our own documentation.

                    The second problem that warenhaus reports cannot be solved by us, so we are downgrading all sites to 9.6.2 again until this is understood.

                    With the proper addressing of Resource path and Resource URL
                    (copy from File Manager path -that does it automatically, why the other one not?- and add ’assets/’)
                    one sees the thumbnails of the images in the Resources Browser,
                    however clicking on an image does not ’move’ it to the ’insert/edit’ preview window...

                    somehow the addition ’(preview)’ gets stuck to the images-URL, but when you erase that nothing happens.

                    but effectively our users cannot place images in their websites.
                      • 17340
                      • 70 Posts
                      We now know that the Resource path

                      should be same as the automatically formed address in the File Manager path with ’assets/’ added.


                      The Resource URL however (one line down in the Configuration sheet)

                      should be NO MORE then just ’assets/’ in it and it all works fine!