yes i installed the super menu module, created a menu and associated it with the zone i created called mainmenu.
Then i pasted the code to get the plugin into the _topmenu view being called from the paged layout, with in the “reddy” layout.
I tested the scenario you outlined (same zone name, same layout, same view), and I was able to get the menu to display (even straight pasted the code you provided). Is the view cached by any chance?
Have you tried passing the menu’s slug to the plugin?
E.g. #cb.getPlugin( plugin=“SuperMenu”, module=“SuperMenu” ).renderIt( slug=“somemenuslughere” )#
hi
i tried the slug version as well.
In the super menu config, the pages i added to the menu have a context popup showing “the content is expired and no longer valid”.
The page entries in the menu are a dark brow colour at first then as soon as you save they go pink.
i copied the content box files from the cf10 server to railo.
It works on railo, although the menus are not nicely lined up.
Any idea why supermenu works only in railo?
Ah, you’re on CF10? I did not test it on 10. I’ll take a look. Thanks for letting me know.
Re: the menus lining up, that is something you’ll have to modify via the theme. SuperMenu only produces a very generic unordered (or ordered) list, which you can then style to your heart’s content.
Thanks for your patience with this. I figured out the issue…apparently, CF9 and CF10 handle the isNull() on one of the content properties differently, so it was thinking that all of your content items were expired, and hence didn’t show them ( I assume the menu items in the menu manager were all red, right?)
If you get a chance to try it out, let me know if it solves the issue. If you just want to update the files, the only changes were in the following:
model/SuperMenuServie.cfc
plugins/SuperMenu.cfc
As far as how you were implementing it, that should all be fine. Once you drop these changes in and reload the app, it should work.
Good luck, and thanks again for helping me squash this.
Yes, that would be awesome. Off the top of my head, I have a couple ideas.
First, it’d be cool if there was a general notifications area (widget updates, content box updates, etc.). Clicking on this icon/link/whatever could take you to a page that shows an itemized list of all available updates, categorized by type (system, widget, module, etc.)
In the individual sections of the admin, it’d be nice to see some visual indication that certain items in the list are updateable (and perhaps have new action icons for quick updating)
For modules in particular, it’d also be nice to push through messages to the main interface (would have to be part of a generic modules construction definition) of the module. That way, if you don’t often hit the “Manage” screen, but frequent other modules, you’d be able to see a prominent note about an update being available.
Not sure about cross-browser feasibility, but maybe the updates could be announced as in-browser notifications?
Perhaps this already exists, but I would really like to be able to subscribe to Forgebox emails to know about new widgets, modules, etc.
Thanks!
Do you mind creating a ticket for this and adding all of our ideas. I think also offering a notification API is key. Where modules layout widgets etc can send notification to the ui in a standard API.
Updating of the module for example seems like a complete overwrite