On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • Does anyone know of RTE that supports "invisible elements" like Dreamweaver? It would be great to be able to extend it to support Snippets, Chunks, TVs, and Placeholders. It would be helpful to let editors know that they should not be editing snippets inside the content area.

      DropboxUploader -- Upload files to a Dropbox account.
      DIG -- Dynamic Image Generator
      gus -- Google URL Shortener
      makeQR -- Uses google chart api to make QR codes.
      MODxTweeter -- Update your twitter status on publish.
    • Hiding elements seems counter to "What-You-See-Is-What-You-Get"
        jpdevries
      • Indeed, hiding elements is a good way to have editors accidenally delete the whole bit where the element tags are supposed to be. What is needed is for a modified RTE that absolutely ignores MODx tags - no messing around with the & in them, no "forced root block" enclosing them in p (or whatever) tags.
          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
        • Quote from: sottwell at Aug 18, 2013, 05:58 AM
          Indeed, hiding elements is a good way to have editors accidenally delete the whole bit where the element tags are supposed to be. What is needed is for a modified RTE that absolutely ignores MODx tags - no messing around with the & in them, no "forced root block" enclosing them in p (or whatever) tags.

          Ignoring MODX tags is a battle I've yet to win with Redactor. One of the challenges is the nature of JavaScript is to decode entities like [ and ] when interacting with .html() like most RTEs do.

          Ideally, I'd like to make that never happen inside pre or code tags.
            jpdevries
          • Quote from: dinocorn at Aug 18, 2013, 05:32 AM
            Hiding elements seems counter to "What-You-See-Is-What-You-Get"

            No, in fact I mean the opposite. I suggest we create visual symbols to represent tags in the editor, perhaps lock them based on permissions. I would like to prevent editors from accidentally altering them, or give them a better understanding of the options available.

            OOPS, I just realized I mocked up the symbols within code editor and not the WYSIWYG editor! Imagine it in the one of your choice.


            [ed. note: bwente last edited this post 6 years ago.]
              DropboxUploader -- Upload files to a Dropbox account.
              DIG -- Dynamic Image Generator
              gus -- Google URL Shortener
              makeQR -- Uses google chart api to make QR codes.
              MODxTweeter -- Update your twitter status on publish.