Page 1 of 1
Re: CMS 0.13 Bug in {sitemap} when start_element is specified
Posted: Fri Jun 30, 2006 2:59 am
by Ted
Honeslty, I think the sitemap tag should go. Menu Manager does everything that sitemap does and does it right.
I'm all for just making {sitemap} call menu manager with the default settings. Thoughts?
Re: CMS 0.13 Bug in {sitemap} when start_element is specified
Posted: Sat Jul 01, 2006 2:39 am
by Ted
Basically, {sitemap} would just be a wrapper around {cms_module module='menumanager'}. This way we still have the intuitive tag name, but you still get all the benefits of menu manager, like calling the parrameters that you said above.
Re: CMS 0.13 Bug in {sitemap} when start_element is specified
Posted: Sat Jul 01, 2006 10:32 am
by westis
Yeah, using the same wrapper for sitemap as {menu} for menu manager would be great. Then it would be much easier to style the sitemap too. We could include a default template for the sitemap for menu manager, although with no template it would still be a normal list.
Re: CMS 0.13 Bug in {sitemap} when start_element is specified
Posted: Tue Jul 11, 2006 4:40 pm
by nils73
Now, that is a great idea, Ted! I never thought about using MenuManager for sitemap ... doh! Stupid me! Making {sitemap} a wrapper would be oh-so-cool! Just another reason to fall in love with CMSMS ... (yeah, I know that I should come up with a website for this but I have to spend some more time on a CMSMS project right now).
Regards,
Nils
Re: CMS 0.13 Bug in {sitemap} when start_element is specified
Posted: Tue Jul 11, 2006 4:42 pm
by Ted
Re: CMS 0.13 Bug in {sitemap} when start_element is specified
Posted: Wed Jul 12, 2006 5:33 pm
by nils73
Yep ... for example. Or: Why.I.Dislike.Any.Other.CMS.Than.CMSmadesimple.org ...
