We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31979
    • 26 Posts
    Is [[UltimateParent]] broken in 0.9.5 ?
      www.waso.com
      • 25663 MODX Staff
      • 12,272 Posts
      I don’t believe it is in the current SVN trunk, no. Working on a third beta release ASAP.
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 7923
        • 4,213 Posts
        Yes it was in some revision. Get the newest one from resource repo.


          "He can have a lollipop any time he wants to. That's what it means to be a programmer."
          • 31979
          • 26 Posts
          Thank you for your fast answers. laugh
            www.waso.com
            • 13993
            • 100 Posts
            When I click on the Feed link in the default template I get the following error

            modxcms.xuru.com/feed.html

            XML Parsing Error: not well-formed
            Location: http://modxcms.xuru.com/feed.html
            Line Number 130, Column 12:
            if (!o && d.getElementById) o=d.getElementById(id);
            --------------------------------^

              • 6221
              • 36 Posts
              Just found that when using Fckeditor and inserting images the path gets absolute although I have answered "yes" in the "rewrite image paths"

              I am not sure if this should get reported to bugtracker or not, but the problem exists and it is anoying since I must manually change to a relative path when changing site from development to production

              EDIT: After more testing it seems that the image rewrite might work, although not very good, it seems that if I manually change the url from http://homepage/assets/images/image2.jpg
              to
              /images/image2.jpg
              it adds the http://homepage/assets part , and the next time i go into fckeditor to change the link it has become "static" again..
                • 8439
                • 89 Posts
                Quote from: ed at Sep 20, 2006, 07:30 AM

                I can’t get file browsing in the TinyMCE insert/edit link feature to function.

                I create a new document, type a word, double click that word then click the insert/edit link icon.

                If I then click the General/LInk URL browser icon I get an empty display, no files visible, no navigation possible.

                One thing, the browser window says "FCKEditor editor Resources browser", a bit of a surprise as I didn’t include FCK in my installation. So how do I fix my problem? do I need to install FCKedit?
                I just tried to upgrade my rev1417 site and FCKedit isn’t even an option. I have now tried installing FCKedit and it has made no change.

                So I am now reporting a bug - TinyMCE wants to use the FCK resources browser to support link editing, this is not part of the rev1417 install. I have mcpuk/browser.html which composes the file browser dialog, however the resulting dialog is useless as noted above.

                The file browser dialog says 127.0.0.1 - Insert/edit link, clicking on the browse icon next to link url opens a blank and functionless browser dialog again for 127.0.0.1.

                This is IMHO a fairly serious problem, could someone please confirm and suggest a fix or workaround.

                [EDIT] have filed a bug report

                Ed
                  • 10487 MODX Staff
                  • 1,535 Posts
                  This is IMHO a fairly serious problem, could someone please confirm and suggest a fix or workaround.
                  I’ve tried this out on my live test site that’s running rev1417 and I’ve had no problems using the Resource Browser from within TinyMCE.

                  TinyMCE wants to use the FCK resources browser to support link editing, this is not part of the rev1417 install
                  It is, the resource browser (which can be used for both FCK and TinyMCE) is located under /manager/media/browser/mcpuk/.

                  Couple of questions:

                  1. Have you tried creating a new folder from within the Resource Browser? Does the folder appear or is there an error message displayed (or worse still, absolutely nothing happens)?
                  2. What are the file extensions of the files you are trying to access? Are they included in the ’AllowedExtensions’ parameter within /manager/media/browser/mcpuk/connectors/php/config.php?

                  I’ll have bit more of a think about this but nothing obvious is really springing to mind.

                  If you wish to log a bug, then don’t forget to add it here: http://modxcms.com/bugs
                    Garry Nutting
                    Senior Developer
                    MODX, LLC

                    Email: [email protected]
                    Twitter: @garryn
                    Web: modx.com
                    • 8439
                    • 89 Posts
                    Quote from: garryn at Sep 22, 2006, 05:49 AM

                    TinyMCE wants to use the FCK resources browser to support link editing, this is not part of the rev1417 install
                    It is, the resource browser (which can be used for both FCK and TinyMCE) is located under /manager/media/browser/mcpuk/.

                    Couple of questions:

                    1. Have you tried creating a new folder from within the Resource Browser? Does the folder appear or is there an error message displayed (or worse still, absolutely nothing happens)?
                    2. What are the file extensions of the files you are trying to access? Are they included in the ’AllowedExtensions’ parameter within /manager/media/browser/mcpuk/connectors/php/config.php?

                    I’ll have bit more of a think about this but nothing obvious is really springing to mind.

                    If you wish to log a bug, then don’t forget to add it here: http://modxcms.com/bugs

                    I did create a folder and it worked, I then discovered that the browser was looking at assets/files and would not navigate upwards (I was looking for files in the site root). By trial and error I discovered that the Resource path and URL set up in the configuration cause the browser to look within a files sub-directory. If I create e.g. a pdf there the browser can find it.

                    I have amended my bug report asking for it to be withdrawn as I couldn’t find a way of doing so
                      • 10487 MODX Staff
                      • 1,535 Posts
                      I have amended my bug report asking for it to be withdrawn as I couldn’t find a way of doing so
                      Glad you got it working! smiley I’ll close off the bug report for you.
                        Garry Nutting
                        Senior Developer
                        MODX, LLC

                        Email: [email protected]
                        Twitter: @garryn
                        Web: modx.com

                      This discussion is closed to further replies. Keep calm and carry on.