Modx vesion 0.9.6

When you are logged in and not in the manager, Modx modifies the code of the public page for you to include the quick edit bar.

If you build a valid template, and are not logged in, what you see will be valid.

Thank you very much for your patient responses. I understand a little better now.

My objective was to try and convince a rather stubborn set of Internet professionals as well as lay decision makers to use Modx or at the least stay away from some other inflexible and one expensive CMS. I have partially succeeded but the responsibility of designing the site is now on my table.

I have never used a computer for more than menu driven application packages related to my regular work. I am however able to work with Modx and hope to learn a new trade in the process.

I have since changed the template from ModXHost. I have ported Wolfgang’s Multiflex 3 column template to modx.
Now I am working on more little nags in the new template .

By now I am confident enough not to ask for help before trying.

I believe there’s a fairly in depth port of Multiflex already done ... with lots of comments discussing how to do things. You might search for it for ideas too.

Regarding search snippets, Hyperflexsearchform makes a good substitute for AjaxSearch, and I’ve found it a lot more flexible (you can search groups of documents or those using specific templates). My version also searches Maxigallery descriptions and my half-built native forum code as well - I need to get that uploaded to the repository here at some point.

Regarding QuickEdit - if you don’t want it, you can easily disable it through the modules menu in the manager (Modules/Manage Modules - click on Quick Edit and set Module Disabled). It was one of the first things I did when I ran into validation issues.

Jon

Thank you .
I didn’t realize that multiflex was already ported. I looked at the porting and found answers to my remaining problems.
I have one question.

I had ported the template without breaking it up into chunks and it seems to work fine. I understand that breaking it up into chunks allows a lot of flexibility. Are there any other advantages in breaking a complex template into many chunks? or conversely, will i or my users run into any problems later if i dont break it up?

Thanks for all the support people. I never cease to wonder at the magic of open source communities. Total strangers, pitching in, helping out, supporting each other from all over the world. This is one example I would never stop talking about to my trainees.

I have found little need for chunks, personally. They work great it you have a lot of templates with sections of code that need to be the same across the board (like a footer). Your design will work just fine not using chunks, and it is easy to add them later if you find you need the flexibility.

An added benefit I could see is that you can train non-administrator users to update chunks without looking at the HTML template. Perhaps in a scenario where the chunk represents contact information that might change.