Yes, at least I think so. A assume you mean the "Clear all caches" button in "Setup"? Anyway I have just done that again and I still have just the top menu.
By the way I can successfully edit content so I am 'talking to' the right database.
ezwebin (Website Interface) does not support changing the menu layout from the admin interface. It is only possible by getting down and dirty with the templates at the moment.
Alternatively you can reinstall eZ Publish using the 'plain site package', but you'll get the eZ Publish 3.8 design and no front page editing.
<i>ezwebin (Website Interface) does not support changing the menu layout from the admin interface. It is only possible by getting down and dirty with the templates at the moment. </i>
So what are all Menu Configuration bits in the Admin interface for then? It's a bit confusing to give no indication at all that they're "not yet implemented" if that's what the problem is.
Are there any other parts that aren't working yet?
As a corollary, are there any 'ready rolled' alternative layout templates available that one can copy and use?
As I said, you can use the plain site package instead of the website interface. Then you'll get the 3.8 and lower design witch does support changing the menu from admin.
> As I said, you can use the plain site package instead of the website interface. Then you'll get > the 3.8 and lower design witch does support changing the menu from admin.
Now I'm even more confused! :-)
Is that the choice you make towards the end of the installation? Is the main/basic difference that you don't get the ability to edit the site from the site itself with the 'plain' interface? (i.e. you can only make changes from the admin interface) Does it otherwise look basically the same when installed?
Is that the only part of the admin interface that doesn't work with the website interface? Is the intention to make it work in the future?
Chris, I'm glad I found this thread as I'm working on the same issue myself.
It seems like users are currently forced in 3.9.0 to choose between two evils.
a) Use the eZ Web Interface which makes it fairly intuitive for editors to be able to modify pages on the site (as seen in the Flash demos on the homepage), but be unable to adapt menus? Crazy.
or
b) Drop the eZ Web Interface which is a main driver for adoption just so you can edit menus. Crazy.
I'll update this thread later if I sort out a method because its precisely the dirty bog I'm wading through at the moment.
Website Interface currently support only flat top and double left menu. It is not decided yet to provide support for other menu combinations. Functionality in admin interface is compatible with old packages used before 3.9.0 as André wrote.
If you want you can add menu management by yourself in pagelayout, you are free to change templates, customize design etc.
Here is a tpl example
{menu name=TopMenu}
{menu name=LeftMenu}
You can replace top and left menu code in pagelayout with code above. Then it will be load dynamically.
You can also use "base" design instead of ezwebin design which supports menu management too, however you will need to move styles by yourself.
Note that ezwebin uses also better layout setup which is not compatible with old one.