NoPic eZine
  
Home
phpWebSite design aid
phpWebSite Main
phpWebSite Forum 1.x
phpWebSite AT (Rene)
phpWebSite DE,EU
phpWebSite DK (Kenneth)
phpWebSite Community
phpWebSite Manual
phpWebSite SupportForum
phpWebSite Wiki
Impressum/Imprint
Datenschutz/Policies
dc4db eZines
 

   en

1.4.2.Convert Menu(s)

Old menus view

From a 0.10.x site, menus look (sometimes ugly) like:

(Views from menumanager - menus and menuitems)

To administrate menus is pWS 0.10.x, some screen interactions were required to build a menu hierarchy. There were one or more menus, shown in a menulist. Each menu had menuitems, declared in a sequence and hierarchy. The menuitems pointed to internal pages (like pagemaster pages), to external pages (like own html pages) or new windows (that opened another webbrowser window). Menuitems could be of state active or inactive. The hierarchy of the menuitems was changeable up and down, but not accross levels. In pWS 1.0.0, the administrative tasks to maintain menus require very less interactions and the handling becomes smarter. There are also hierarchies and menuitems, although the last term is not more used and now called menulinks. To a menu may added a link or other link. Both cover a bit the older terms internal and external references, but at all are not quit the same. One attribute, to be active or inactive, at the moment does not seems being implemented.

Convert menu and menulinks

One link within the convert utility leads to the menu conversion.

Of course, module menus have to be installed before convert can run. If not, you get the nice response

...but you are not as beside as the author was, and you will see

that means, a menu has converted and the menuitems (the menulinks) have now to convert step by step ...

In the best case, the final response is

Converted menulinks

The menu and menulinks are always visible. To modify something, switch the link admin mode on. Javascript icons suggest the actions you probably want to perform.

Menus converted, conclusion

Menu conversion requires some observations when finished. Both, active and inactive entries are converted. But that state seems not more present and all menulinks will be visible. A manuel verification of the sequence and the level hierarchy of the menulinks is also neccessary. I observered some strange placements, those were easy corrected, but required a little work. Some former menuitems, pointing to any pWS modules not more or just not available at the new site, will result to a call of a 404 page not found message. Such menulinks should be removed. And at last, all single menulinks should be verified if pointing to the intented items. Remember the cases of assigned webpages IDs, that may have vary.

Copyright © 2006, VbID Verlagsbüro GmbH
pWS modules dcP, dcT, dc4db, Copyright © 2006, VbID Verlagsbüro GmbH
This Site is powered by phpWebSite © The Web Technology Group, Appalachian State University