We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25317
    • 122 Posts
    Quote from: Mark at Nov 03, 2005, 08:15 PM
    Do you get the error on a fresh install on the same server with default content?

    Sounds like a bad upload b/c in IE 6 it works fine here.
    On further checking, I have two localhost (XP IIS) installations, one clean, the other an Eto upgrade. Both experience the problem. Inserting an image is fine, but selecting to browse the server from an existing image properties dialog seems to throw the error.

    I have tested with Firefox and IE. Firefox does not seem to be affected, perhaps just an IE specific syntax bug?.

    Regarding the missing image/place holder mentioned. This may be a seperate issue. Only the upgrades show’ed this trait in Firefox and IE. But then, new installations don’t have an existing image to test with, new inserts work as the should in both.

    I have noticed that in looking at the image properties of both upgraded document images and newly inserted images, the new images have the complete image path on the server (http:// ... /image.jpg), whereas the upgraded path starts at the assets directory.

    Rewrite image paths is set to yes on both (as was on eto before the upgrade). Maybe the solution is just to delete and reinsert the images.
      • 2408
      • 1 Posts
      i went to www.opensourcecms.com and copied their "chunk" code for the two chunks that relate to login and overwrote my installations chunks with their code. Works fine now.
        • 6726
        • 7,075 Posts
        The "Clear Keywords" button in Document Settings doesn’t seem to work : it does not clear the keywords, nothing happens.

        Edit : Since there’s no answer, I’ll check FlySpray for bug reports...

        Edit2 : No bug report, I have submitted a ticket :
        http://modxcms.com/bugs/index.php?do=details&id=114
          .: COO - Commerce Guys - Community Driven Innovation :.


          MODx est l'outil id
          • 25317
          • 122 Posts
          Quote from: Robsta at Nov 04, 2005, 04:12 AM

          Regarding the missing image/place holder mentioned. This may be a seperate issue. Only the upgrades show’ed this trait in Firefox and IE. But then, new installations don’t have an existing image to test with, new inserts work as the should in both.

          I have noticed that in looking at the image properties of both upgraded document images and newly inserted images, the new images have the complete image path on the server (http:// ... /image.jpg), whereas the upgraded path starts at the assets directory.

          Rewrite image paths is set to yes on both (as was on eto before the upgrade). Maybe the solution is just to delete and reinsert the images.
          Could this be a ’Rewrite image path’ editor integration issue? Reinserting the image onto the page, the absolute path appears in the URL field of the insert properites dialog (from http://...). The image is not found in the editor when the relative path is used (as from the upgrade). Both display on the page fine. Or does the FCKEditor display the rewrite paths differently to HTMLarea?
            • 19004
            • 33 Posts
            Quote from: Robsta at Nov 03, 2005, 07:43 PM

            I get an error with the FCKeditor. This occurs both using Quick Edit, and from within the Manager. The site is an upgrade from Eto to Modx on a live server (my test address), using IE6 browser.

            When I edit a page with an image (the image appears in the page editor in the manager, but shows placeholder/not found using QuickEdit), right click on the image, select ’Image Properties’. Click on ’Browse Server’, I get a scripting error:

            Line: 369;
            Char: 3;
            Error: ’null’ is null not an object;
            Code: 0;
            URL: http://www.domain.co.uk/assets/plugins/fckeditor/editor/dialog/fck_image.html

            Any ideas?

            I’m having this exact same issue. I’ve tested on multiple machines with both IE6 and IE7. Same error in both. Has anybody found a solution to this?