firstlevel menu names with reserved values?

A place to report and discuss bugs - please mention CMSimple-version, server, platform and browser version
Post Reply
manu
Posts: 1086
Joined: Wed Jun 04, 2008 12:05 pm
Location: St. Gallen - Schweiz
Contact:

firstlevel menu names with reserved values?

Post by manu » Thu Mar 26, 2009 10:43 am

A bug or a feature ? I doupt.

If any of the "reserved" values (i.e. "download","mailform", "guestbook" etc.) are used as first level (h1) keys, the output in edit- and viewing-mode are unpredictable.
This is an issue in my opinion.
Is there a complete list for the "forbidden" titles available?
best regards
manu

mvwd
Posts: 299
Joined: Tue Jun 17, 2008 10:35 pm
Location: Baden Württemberg / Germany
Contact:

Re: firstlevel menu names with reserved values?

Post by mvwd » Thu Mar 26, 2009 5:18 pm

...wow. I can't believe, nobody found out this issue until now... Maybe there are some informations in the old forum?

All the 'reserved' words are:
'download', 'function', 'search', 'mailform', 'sitemap', 'text', 'selected', 'login', 'logout', 'settings', 'print', 'retrieve', 'file', 'action', 'validate', 'images', 'downloads', 'edit', 'normal', 'stylesheet', 'passwd'
... AND anything, added via initvar(). Maybe some of the plugins used to init some variables this way.

Not all words result in a chaotic behavior, some do what their name supposed to do.... I made a little list, what happens if a keyword is used as <h1> in both states (logged in / out):

[ external image ]

In my opinion, this is a bug!

mvwd.

Post Reply