TemplateManager Plugin - Proof of concept

thanks xpix, what I do now is to add the script at the top of the welcome page
of the manager, but it is a pain in the Ars Anatomica to put it and get rid of it
everytime I have to go in...

I was hoping for something automatic that recognizes de admin and the tree
appears... but it is no a matter of life or death.... thanks anyway...

There is a wiki post on customizing the manager home that explains how to close the tree. Then you can have 2 themes, one with the tree visible and the other without and assign the correct theme to each user.

aha... as always Shane you are great!! Thanks, that is it, solved...

Two themes, why dont I think of these things? Thanks again...

PS I think I need your help in this thread: http://modxcms.com/forums/index.php/topic,32747.0.html

Mootools help

I need to build in mootools the equivalent of the flowing line in jquery

$("div:contains(’John’)").css("text-decoration", "underline");

I need to filter based on text. I could not find anything similar at http://docs111.mootools.net

Thank You

Cipa,

How’s progress on templateManager?

cheers/k

I’ve been busy

I have the framework in place but there are to many fields and functionalities to implement.
Do you need some kind of functionally for a project?


Edit:

The following functionalities work:

Set Child Template ID
Hide Title field - could be easy extended to the rest of the fields
Modify the name of a field - could be easy extended to the rest of the fields

TODO
required fields
default values for fields
hide tabs
hide/show fields for user groups

OK, understandable...I don’t need it for a project at the moment but have been interested in it since the beginning. Thanks for your efforts!

/k

I will try to release a version soon and see how it goes.

Thx for your interest

Quote from: ChuckTrukk at Feb 04, 2009, 05:18 AM

Wouldnt it be nice if templates had parameters similar to snippets, plugins, modules?

This has a lot of merit. You could set up properties that could be accessed via API methods with the templates and valuable meta information and control rules could be stored there instead of in TVs. Anyone else see compelling reasons not to do it?

Some times ago I have ideas like your: automate MODx templates.

And I resolved this by adding special block in template description string like this:


With plugin QM (QuickManager) I process all additional template params like "children" and "pagetitle".
And now I can easy set children template(s), pagetitle generation format, auto-alias, tablename (for Quid plugin), class (used by QM for manager interface auto-modification) and all I need.

If this conception is interesting to you, I can share sources and more information.

P.S. Speaking english so-so, hope you understand me.