I am actually seeing some similar problems, with some doubled prefixes and odd groupings. I am wondering if it might not be easier to have people define groups to match on, though of course, then it becomes less automated.
Still, even with the problems, its reducing the size of my massive publish list, so I am using it.
Linda and Rob, I’ve updated the extension again and it’s now grouping correctly (without doubling up names). So, let me know if this is any better, if not I may resort to user defined groupings, although I’d rather not.
Just an fyi - I noticed that the nested weblog extension does not work with the Publish Tab Behavior setting “On Click” (admin › System Preferences › Control Panel Settings ). When the setting is set for “On Click” the publish tab performs like the hover behavoir but is not clickable.
Very odd. I downloaded the extension again, uploaded it and checked the extension manager. It now says 1.0.7. But I am not seeing any change in the grouping behaviour at all from the previous extension. I even tried disabling and reenabling, but still no difference. Could it still have old settings, somehow?
@Rob Q: Yes, I’m aware it doesn’t work with the “On Click” setting, this is because it’s implemented using pure CSS, if the demand is there for an “On Click” mode it can be added, but I always just thought of the “On Click” setting as a way to avoid the screwy JavaScript EE implemented on the menu.
Alright 1.0.8, hopefully, fixes Linda’s bug and keeps all the prior bug fixes intact. I rewrote the parser once more :-D, so go get it at the top of the thread!
I wonder, btw, if it is possible to go in and hand-edit the width assigned to the submenu? I doubt most people would need it, but my weblog naming scheme has givem me some very long ones, and one or two end up wrapping onto two lines.
Sure thing, just open up the extension file and search for 200px. Change that to your new width. Then search for 190px and make that 10px less than what you changed 200px to. Both those changes should be within a CSS declaration.
Mark, this extension is just what i needed, great!
But how do i get it to work with a german (or other) language version selected in the personal cp settings?
Just copying the language file to that folder didn’t do it.
I found that this extension does not work if I have the cloner extension put out by Paul that it doesn’t work with this extension. Any way to resolve this?
This is a problem in Paul’s extension. If anyone from EE is listening in on this thread can we get the cloner extension to use the $EXT->last_call var? Thanks.