Greetings. I am building a new site with MODx 0961.p2. One of the site pages has content distributed over are a three-column (table-less) layout. I need to be sure that it is easy for my client to modify content in all three columns of these pages. My strategy was to place the content associated with each column within a separate chunk, and then appropriately call each chunk from within the template that defines the page in question. Is this the best way to do this? Ideally, I would have liked to just place the content for all three columns directly into the page (without the use of chunks) and then just use the [*content*] placeholder in the template. However, I was not sure how to do this and still offer the client the ability to easily make updates to the content for all three columns.
Any insights on this would be great. Am I missing a more reasonable approach? Should I avoid the extensive use of chunks to place textual content in pages?
Thanks folks.
- Marconi
just use templae variables
then you could create a TV for each column [*columnleft*] and [*columnright*] or what ever name you want to give them.
Thanks Dimmy. Yeah, I figured that TVs might be the way to go. I am still not very experienced with them though, which is why I did not try implementing them from the get-go. I will give your strategy a try though.
Again, thanks for the tip.
- Marconi
Hi Marconi,
The trick is to set your two TVs as "Input type: RichText". This gives your client full WYSIWYG editing in both columns, as he has in the [*content*].
Steffen -
Thanks a lot for the tip. I tried what you suggested and it does in fact allow the client to update the content defined within the variable. The problem I am now having is that the editing capability remains even when someone is normally viewing the site (not logged in). So, the question: How do you give the client the ability to edit the TV content, yet keep the WYSIWYG functionality from showing up when someone is viewing the site normally? I notice that you can select ’Rich Text’ as both an ’Input’ type as well as a ’Widget’. What are the proper selection settings here?
Thanks again for your support.
- Marconi
Ah, ok, that’s because you chose a widget. You need it as your input type. Then you’ll only be able to edit it from within the Manager.
Hi Steffen -
Yeah, I tried that. If I only select ’Rich Text’ as the Input Type (and not also the Widget), the WYSIWYG editor does not show up. The editor only shows up if I select ’Rich Text’ as the Widget. And then, as I indicated before, it ALWAYS shows up, whether you are logged in or not. Something is obviously not right. Not quite sure how to resolve this.
You need to edit the document in the manager. Then you will see that there’s a new editor below the standard content-editor.
You won’t be able to edit it from the frontend, only the manager. That’s the way I do it myself, If you want to edit it from the frontend, then you’ll need something else, which I haven’t dived into yet.
Marconi,
You do not want to set a widget. Just leave that blank. Then once your client is logged in as the manager they can make the changes themselves. They just choose it from the quickedit menu, or you could use the [*#tvname*], that way a button will appear next to the designated TV.
Hey Steffen -
I think you may have misinterpreted what I said in my previous post. The problem is that the editor always shows up, even in the front-end when you are simply viewing the site as a non-administrative user. I only want the editor to show up when someone logs into the site as an administrator, but it is showing up all the time. Setting the Input Type to ’Rich Text’ does not make the editor show up at all, ever. But if I set the widget to ’Rich text’ then the editor shows up ALL the time -- even when you view the site as a non-administrator. I just want the editor to show up for folks who are logged in to the site with administrative rights. I can’t seem to get this to happen.
