We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24520
    • 14 Posts
    I would like to have an option or be able to hack it somehow - to choose whether the template I’m creating has content (the plaintext/richtext section). As I understand right now, this section is obligatory and I suspect even that it’s a result of a certain design decision (because event containers/folders could have content, which does not make sense to me, really, but I can imagine a rare situation it is useful).

    Basically right now I’m working with a rather big project with MODx. Not only I am creating pages, but also "content", which is not really a browsable page. I have my structure divded into /pages and /content, and pages under /content are pages as well, but they hold only data (think of it as xml), let say : News Item, Product, Release, Event, etc. I’m using TV’s for those templates, to have fields like date, name, author, etc. The problem is that the big content field still persists, tempting user to ommit TV’s and paste some text directly into the content field. I’m also using special formatting and logic for those TV’s and I just don’t want to make user think.

    Any idea how to achieve that?
      • 36624
      • 535 Posts
      hi,
      maybe you should look here : http://www.modxcms.com/ManagerManager-1565.html
        CTRL+SHIFT+U - Clear Cache
        CTRL+SHIFT+H - Hiding Heft Panel
        CTRL+SHIFT+N - Fast Create Resource
        CTRL+ALT+P - Preview Recource (in edit resorce window)
        CTRL+ALT+S - Save
        • 7231
        • 4,205 Posts
        manu beat me to it...but this is what I was saying grin

        If you are talking about hiding the content box in the manager, you can use ManagerManager plug-in to hide those fields. To keep them out of the front end editing don’t include the # in the call [*content*] rather than [*#content*].

        One thing to consider is that the document variables (pagetitle, longtitle, content,...) use less overhead than template variables. I find that by renaming the standard fields (using ManagerManager) you can often adapt the standard fields to conform to different uses.
          [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]
          • 24520
          • 14 Posts
          Thank you for your answers, it seems right it is the thing I need, especially that it can be set for each template. The renaming trick also looks useful (well, as long as my variables are Strings, not let’s say Combobox or Date, but still, I get the idea).

          @dev_cw - by hiding out of frontend, you mean QuickEdit, right?
            • 7231
            • 4,205 Posts
            by hiding out of frontend, you mean QuickEdit, right?
            Yes, quickedit.
              [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]