We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34162
    • 1 Posts
    Hi

    I dare to ask another question in this forum, sorry for nagging. (please see also attachment)

    I try to edit some resource content in Evolution 1.0.2 but editing is limited to simply typing in text and change font style. the rest is pretty useless, like adding a picture or even positioning the picture, boy, don’t even try it!

    First, why is MODx forcing me to keep every picture in the image folder? Maybe I like to have subfolders under the image folder, maybe I want to have complete different/extra image folder somewhere in my directory ... bad luck - MODx decides for you to have all images stored in the ONE and ONLY image folder. Why is that? In the screen shot it even shows only the image folder, although I have several subfolders set up. HOWEVER, there is no way I can choose any of these subfolders?

    Then again ... WHY is there an opting given for "html" edit, it’s a little joke, really. Oh sure, I can switch to html edit and even type in whatever I like, wait, it gets better, it even allows me to "SAFE" it ... the only thing is, it never gets saved! is this a bit of a ...what joke?

    I apologize for my cynics here and if that disturbs anyone - just don’t answer, but this is really not fun. It it’s there, if it gives you the option but actually really isn’t there and ins’t an option neither then why have it there at the beginning?

    I have no idea how this FCKEditor works with other people here but it certainly doesn’t do the job on my site! Which, all in all, brings me back to everything hard code and that doesn’t do it for a CMS, or do I miss something?

    I tried for a whole day, back and forth and offline and online (ah - offline is even worse as it throws me even an "Internal Error" (screen shot) when trying to upload an image) before I added this post, so I may sound a bit frustrated and impatient here. But that I am. I really like MODx but there are quite a few things they contradict.

    So, sorry for that but thanks for your understanding

      • 26931
      • 2,314 Posts
      the WYSIWYG editors are third party components and NOT MODx.

      i never came across one of those problems you are describing ( i use TinyMCE )

      First, why is MODx forcing me to keep every picture in the image folder? Maybe I like to have subfolders under the image folder, maybe I want to have complete different/extra image folder somewhere in my directory
      maybe check your paths under
      System configuration -> Interface & Features -> File base path & File Browser URL
      System configuration -> File Manager -> File Manager path

      ...as well as folder permissions
        • 26931
        • 2,314 Posts
        hmmm ... weird, there must be something borked in your installation, although TinyMCE doesn’t work always perfect i’m absolutely able to use different subfolders in "images" / html button works too

        what browser are you using? e.g. Firefox plugins could conflict with TinyMCE’s javascript / Chrome might act weird too
          • 26931
          • 2,314 Posts
          FF 3.5: Evo 1.0.2 and TinyMCE with standard settings ( only one is Entity Encoding: Raw / Plugins -> "TinyMCE 3.2.4.1" ) i’m able to click on the HTML button, wrap a section in a div with an ID and it doesn’t get stripped out / actually you should avoud doing such things with a WYSIWYG editor

          if html elements get stripped out, you could also check the plugin settings "Cleanup" enabled/disabled ... be careful, do all the testings on a test installation. (disabled is not recommended afair)

          you can (re)check the path to your installation:
          http://modxrules.com/articles/get-lost-file-manager-path

          e.g. my local paths look like this:
          File Manager path: C:/xampp1.7.1/htdocs/myinstallation/
          File base path: C:/xampp1.7.1/htdocs/myinstallation/assets/
          File Browser URL: assets/
            • 5340
            • 1,624 Posts
            Are you sure all the files were uploaded correctly?
              • 22303 MODX Staff
              • 10,725 Posts
              Don’t get confused. TinyMCE is the editor; a custom version of FCK - Resource Browser is used as the Resource Browser.
                • 23299
                • 1,161 Posts
                Might I make a suggestion?

                If you are running MAMP locally on your Mac then you can create as many MODx installs as you like. Save the MODx download folder and back it up. Label the archive MODxBase or whatever. You can then copy that into our MAMP htdocs folder as often as you like so long as you give that MODx folder a unique name each time. You can then do multiple installs for testing purposes.

                I find its a good idea to create several test ground installs. On one of them you should try adding the sample content during the install. Leave one or more of your test installs with the default template. With other installs you can build your own template and CSS system.

                The whole purpose here is to have several systems going that will allow you to compare code, snippet calls, chunks, templates, paths to files etc. Then as you explore each snippet or new building blocks you can carefully test them in different environments to get the hang of how they work and connect with the system. Once you feel comfortable you can then try your new learning section out on your "real" project.

                Be sure to take Susan’s wonderful guest user system for a spin on her site at www.sottwell.com as that gives you a real behind the scenes look at how the system goes together. You might want to try some of Mary’s great tutorials at http://codingpad.maryspad.com/beginner-tutorials/

                Bottom line: unless you are very comfortable its best to take little steps to build confidence with this system. Don’t try to do everything all at once with one project site.

                I understand your frustration: I have been there. I had moments where I wanted to throw my computer through the window! Often a good night’s sleep and a fresh attitude in the morning does wonders...

                EDIT: one other thing. I find all the RTE’s are frustrating to use. But RTE’s like TinyMCE are not developed my MODx developers. Using them is limited. You are not going to get full WYSIWYG feedback as you work with content. Its best to move slowly, save often and check the saved document often in a real browser window. I find its also best to be VERY thorough with your CSS file. You do not want to be adding a whole bunch of inline styles with any RTE in my book. If you are using the pull down style tabs in the RTE be sure to check the generated code by turning the TinyMCE preview off. Quite often the RTE is adding unwanted tags etc.

                As far as folders and pictures go I use three systems. All my site presentation images that get displayed with my templates go in my templates/templateName/images folder. All my images that I upload into content pages (some using the RTE image upload system) go in the assets/images folder. I then use a custom jQuerry system to display groups of images. These get dynamically added via the MaxiGallery snippet which creates its own gallery folder system within the assets/galleries folder. MODx lets you build your own paths to images as you see fit. But this system keeps my three categories of images separate without too much confusing image path configuration.
                  • 23299
                  • 1,161 Posts
                  Be careful with scripts in the header.

                  The scripts have to be presented in the right order. The CSS link usually goes first. Sometimes getting MODx, snippets, AJAX Search, MootTools, jQuerry, etc to all behave nicely can be a real chore.

                  Again the best thing to do is build slowly with a clean simple system and template first. Get it working on a basic system or default install and then carry that over to real projects.

                  Its also a good idea to make sure the markup is presented well and that it validates. There are also some good debugging tools and Firefox extensions to help pinpoint issues.
                    • 3749
                    • 24,544 Posts
                    What you’re experiencing is why so many of us don’t use the RTE at all -- for anything. I upload images and files with FTP and do all page editing with the RTE off.

                    It’s also why you’re not getting better help on this. Those of us who don’t use the RTE have little or now idea how configure it or to deal with the problems it causes.

                    I wish I could be more help.

                    Learning to work in raw HTML is definitely worth the effort. Once you get comfortable with it, it’s actually much faster than using a WYSIWYG editor and then cleaning up the garbage that it creates.
                      Did I help you? Buy me a beer
                      Get my Book: MODX:The Official Guide
                      MODX info for everyone: http://bobsguides.com/modx.html
                      My MODX Extras
                      Bob's Guides is now hosted at A2 MODX Hosting
                      • 23299
                      • 1,161 Posts
                      Good point Bob.

                      But if the project is going to be turned over to a client then the RTE will come into play in many cases.

                      I find the trick is making a happy medium work. Sometimes this means very careful CSS structure so that the RTE paragraphs, headings etc will always refer to the CSS file. I also add CSS classes to the RTE for images so that the client can upload and position the images with CSS layout classes that I have added to the design. The Manager Configuration makes this possible.

                      Building a site with a modern CMS that you have sold the client on is not going to sit well if you have to explain why the content editor does not work and that they need to use a FTP program to add images etc...