main content splitting to insert variable blocks

What I said on both accounts holds true. 1.0 will be your true fix, while my other suggestion will get the job done now.

If you go with the TV option, yes, you will need multiple TV’s, but you truely only need one TV in your template. The rest can be managed in the MODx Manager, since you said you didn’t want to keep updating your template.

the mythical 1.0 release, where everything will be perfect

You can manually put the TV’s in the wysiwyg such as:
[*head1*]
[*paragraph1*]
[*list*]

Quote from: captain at Jan 18, 2007, 02:37 AM

sure, i can make chunks or a set of tv’s. but i have to include the tv’s into templates, or chunks, or whatever and then they are on a fix place. and if i want to create/edit a document, i just can fill the tv’s with content, but i can’t move them around, because they are fix in the template.

Chunks or TVs don’t HAVE to be in the template. The MODx parser goes through a number of passes to recursively parse the document in question.

What this means is that you can place [tt][*head1*][/tt] and [tt][*list*][/tt] inside your document content ([tt][*content*][/tt]). Likewise, the same applies to [tt]{{chunks}}[/tt]. And it even goes further that you can have TVs inside chunks, chunks inside TVs, and the parser will keep parsing until there’s no tags left (or 10 passes MAX). Only then is output pushed to the browser.

Personally, I would use the chunk method, because TVs will clutter the document editor. And since this content is "predefined" you won’t need to be editing it every time along with a document.

EDIT: max passes added.

Quote from: sirlancelot at Jun 06, 2007, 10:20 AM

What this means is that you can place [tt][*head1*][/tt] and [tt][*list*][/tt] inside your document content ([tt][*content*][/tt]). Likewise, the same applies to [tt]{{chunks}}[/tt]. And it even goes further that you can have TVs inside chunks, chunks inside TVs, and the parser will keep parsing until there’s no tags left. Only then is output pushed to the browser.

I was thinking this myself, If you define loads of content chunks, and call them block_1 block_2 etc, then a user could simply put them into the content at the position they wish to see them. No template jiggery pokery at all. Just type {{block_1}} in tinyMCE and the CMS of the Gods handles the rest for you .

the neverending thread

You can manually put the TV’s in the wysiwyg such as:
[*head1*]
[*paragraph1*]
[*list*]

sure i can, but how do i specify the specific text (content)? this happens also to chunks. i can just insert predefined text.

thanks for patience!

Once your template variables are created, make sure they are assigned to the template you are using, then they will be available for editing for each document, a textarea (if that is what you chose it to be) will appear in the edit screen under the document content area.

The TV content can then be modified on a per page basis (or left alone and will have the default value you set when the TV was created).

@breezer

yes, i think this is a possible solution, BUT if i want to predefine lots of elements (h1 - h6, p, li, and lots of specific classes, etc.) then i have in the manager a whole bunch of a list with textfields, where i can input my text. this is not very handy, especially for the enduser. i really want get rid of the wysiwyg-editor, because of producing really bad code...

like others had said: for a perfect solution, i have to wait until the release of 1.0.

Quote from: captain at Jun 13, 2007, 07:41 AM

yes, i think this is a possible solution, BUT if i want to predefine lots of elements (h1 - h6, p, li, and lots of specific classes, etc.) then i have in the manager a whole bunch of a list with textfields, where i can input my text. this is not very handy, especially for the enduser. i really want get rid of the wysiwyg-editor, because of producing really bad code...

The 1.0 release will only help if you know PHP. It will allow the programmer to create custom parser tags ([tt][[Snippet]][/tt] and [tt][[^MyCustomtag]][/tt]). Look at the MODx Roadmap.

The way I see it, you’re immediate fix is going to be a delicate combination of Chunks and TVs. At some point you have to sacrifice control for usability. No CMS will accomplish something like you want, javascript RTEs bridge the gap of control and usability. If you want more control of your code, disable the RTE.

Does anyone have any news on integrating XStandard? It might be an alternative answer.

I hate to unbury a dead topic, but this seems to be the closest thread to what I am trying to accomplish:

I have a TV which calls some chunk info etc. This TV is for a sidebar that is optional on every page for my client. In an optimal situation, I could make document optional TVs.

In other words, I want to be able to enable or disable a TV via a checkbox.

Since my client wants the text boxes to possess content only, I have to finagle my way around with the design for the sidebar. If I were able to effectively disable the TV on a per document basis, I wouldn’t have to worry about the client having empty boxes, etc. on the page.

Essentially, I need the ability to "activate":



Without this, the box either appears empty or I have to use multiple templates which makes management more difficult.

Am I clear, or is this confusing?