I know I'm probably not supposed to do this yet but I just updated a 0.11 test site with 0.12beta2.....
I have various problems now and would like to ask if I can expect similar issues with the final:
eg:
I had to remove the cssmenu module otherwise I couldn't get any output from the site or admin, will CSSmenu still be supported in the final release?
I think the new menumanager need a bit of preparation before it will work an I'm worried that I'll have an unusable site until I can set things up again
I have been using the events modeule (from Patricia I think), but this doesn't seem to work anymore - is an update planned? Is there a brief summary of what might need changing
I wonder what other things might need addressing.
I hope none of these issues have already been discussed/clarified - if so I apologise but I've not had time to follow the forums so closely recently. Just point me to a thread or two if so
John
0.12beta menus and modules
Re: 0.12beta menus and modules
How so? I'm open to suggestions.I think the new menumanager need a bit of preparation before it will work an I'm worried that I'll have an unusable site until I can set things up again
-
pinthenet
Re: 0.12beta menus and modules
That's OK Patricia, I think I knew that..... Is there a general guide somewhere about what I need to change, or is it perhaps easier for me to adapt News? I only need something that also supports start/end dates.
Regarding menus - not sure what you mean Wishy.. I suppose I'll have to get the menus working with menumanager on my test site then use the results for the production site. I'll have to plan a longer down time. Ideally it would be good of cssmenu still worked under 0.12, but then you'd need to support all other menus I guess.
I'm also a bit concerned that there may be other suprises lurking... Is/was there a summary - I seem to remember that westis produced a general overview of changes/features.
John
Regarding menus - not sure what you mean Wishy.. I suppose I'll have to get the menus working with menumanager on my test site then use the results for the production site. I'll have to plan a longer down time. Ideally it would be good of cssmenu still worked under 0.12, but then you'd need to support all other menus I guess.
I'm also a bit concerned that there may be other suprises lurking... Is/was there a summary - I seem to remember that westis produced a general overview of changes/features.
John
-
pinthenet
Re: 0.12beta menus and modules
Phew, slight relief.
Now it's daytime again I've looked a bit further and I see how to get the menu working so I can prepare things off-line.
For events I may be able to (mis)use News start/end dates in a special category. Or I'll copy to a new Events and add some of the missing attributes (organisation, locations etc).
Up to now I've usually been able to take a new version without much effort, this time I need to loook more closely.
John
Now it's daytime again I've looked a bit further and I see how to get the menu working so I can prepare things off-line.
For events I may be able to (mis)use News start/end dates in a special category. Or I'll copy to a new Events and add some of the missing attributes (organisation, locations etc).
Up to now I've usually been able to take a new version without much effort, this time I need to loook more closely.
John
Re: 0.12beta menus and modules
westis is due back from his 3 week holiday tomorrow. Then I'll give him a day or so to recover, and then I'll bug him to write that summary page. Most of the major changes involve the menus, and he understands that more than anyone else anyway.
I'll look into CSSMenu on 0.12. To be honest, i just assumed it would keep on working. In theory, you should be able to switch to the cssmenu.tpl template in menu manger and get the same results (it has the same html output as CSSMenu), but the chances of it being a perfect drop-in replacement are probably slim.
If you do decide to do the switch offline from cssmenu to cssmenu.tpl in menu manager, can you share your results here. What you specifically had to do from a user's perspective to get it working...
Thanks!
I'll look into CSSMenu on 0.12. To be honest, i just assumed it would keep on working. In theory, you should be able to switch to the cssmenu.tpl template in menu manger and get the same results (it has the same html output as CSSMenu), but the chances of it being a perfect drop-in replacement are probably slim.
If you do decide to do the switch offline from cssmenu to cssmenu.tpl in menu manager, can you share your results here. What you specifically had to do from a user's perspective to get it working...
Thanks!
-
pinthenet
Re: 0.12beta menus and modules
OK - will do
I should be able to look at it during the week, otherwise next weekend
John
I should be able to look at it during the week, otherwise next weekend
John
-
pinthenet
Re: 0.12beta menus and modules
just a quick question - can I install the MenuManager in 0.11? That would obviously make the transition simpler as it would be possible to switch before 0.12. I noticed there's a Menu Manager in the Forge but it's empty
Re: 0.12beta menus and modules
No, the menu manager relies on code that only exists in 0.12.
-
pinthenet
Re: 0.12beta menus and modules
Status update - cssMenu
after wrecking my Windows installation on Thursday I had to spent most of my time recovering and reinstalling, but I managed to look at the menu yesterday. In my case it was surprisingly easy to get cssMenu working again.
I imported the cssmenu.tpl to the DB then changed the cms_module tag in the template. My existing CSS for the menu worked without modification, although it's more complex than necessary. I removed the
{$node->hierarchy}:
sequence from the template to get rid of the hierarchy numbers at the start of each menu.
I only need to cleanup the CSS and add the javascript to the head for IE and I should be OK, but I need to do that at home as my current IE at work doesn't seem to like javascript in general at the moment.
John
(PS I got the events module working by removing all logging calls)
after wrecking my Windows installation on Thursday I had to spent most of my time recovering and reinstalling, but I managed to look at the menu yesterday. In my case it was surprisingly easy to get cssMenu working again.
I imported the cssmenu.tpl to the DB then changed the cms_module tag in the template. My existing CSS for the menu worked without modification, although it's more complex than necessary. I removed the
{$node->hierarchy}:
sequence from the template to get rid of the hierarchy numbers at the start of each menu.
I only need to cleanup the CSS and add the javascript to the head for IE and I should be OK, but I need to do that at home as my current IE at work doesn't seem to like javascript in general at the moment.
John
(PS I got the events module working by removing all logging calls)
