Quote from: splittingred at Oct 02, 2006, 04:04 PMThose should come after the next release (0.9.5 in late beta now)
- Heirarchical User/Document Groups (i.e., subgroups of user groups would be nice)
- A better UI for managing user Groups
I might have phrased that wrong. I guess the issue is this - If I’ve got a large site with one main template style, but some variation in it according to different departments (which are subdirs in the site), it might be helpful to have a subtemplate within that.
- Ability to assign a chunk as a template var without having to snippet hack itWhy will using chunks not work for this now?
- OR Subtemplates (templates within templates)
- Mass Document group/TV/variable changing (if i want to change 3000 pages to a different document group...and i shouldnt have to download a plugin to do this)The 095 Doc Manager will do this quite nicely.
I might have phrased that wrong. I guess the issue is this - If I’ve got a large site with one main template style, but some variation in it according to different departments (which are subdirs in the site), it might be helpful to have a subtemplate within that.Make a single TV that is a dropdown list selector. Use the dropdown list selector to tell it which "section" you’re in. For good measure, have it’s default value be @INHERIT so you only have to set it for the top level of each section. The value of the options would be the chunks you use as your subtemplates, like:
For example, if I’ve got a header that has different HTML elements (say, extra divs or LIs or something) depending on what department it loads, it’d be much easier to specify to "include" a certain file, or (sub)template in each file. Kind of like how in Smarty you can use conditionals and the "include" statement to include separate files.
Right now I have to do a TV that references a Document ID number, and then use a snippet to "include" that document into the page based upon the TV number. Maybe there’s a better way of doing this, but I haven’t found one yet. Do you have any ideas?
products=={{productsSection}}||news=={{newsSection}}...
I might have phrased that wrong. I guess the issue is this - If I’ve got a large site with one main template style, but some variation in it according to different departments (which are subdirs in the site), it might be helpful to have a subtemplate within that.Make a single TV that is a dropdown list selector. Use the dropdown list selector to tell it which "section" you’re in. For good measure, have it’s default value be @INHERIT so you only have to set it for the top level of each section. The value of the options would be the chunks you use as your subtemplates, like:
For example, if I’ve got a header that has different HTML elements (say, extra divs or LIs or something) depending on what department it loads, it’d be much easier to specify to "include" a certain file, or (sub)template in each file. Kind of like how in Smarty you can use conditionals and the "include" statement to include separate files.
Right now I have to do a TV that references a Document ID number, and then use a snippet to "include" that document into the page based upon the TV number. Maybe there’s a better way of doing this, but I haven’t found one yet. Do you have any ideas?
products=={{productsSection}}||news=={{newsSection}}...
Make sense?
much more simpler ... MODx parser lacks of a basedir variable for implementing absolute inner site links.
i’m still looking forward to hosting subsites and sites on different domains. the subsites hack is ok, but doesn’t work well across different domains...
<a href="mydir/mypage">even if you call it from the forum subdir (for exemple)
<a href="/basedir/mydir/mypage">