Edit Menu extension

Updated version 1.1 adds FT-E compatibility.

What’s FT-E?

Sorry for what is probably a very daft question - far too little sleep this week.

Best wishes,

Mark

Fiery Tea Expansion

Fiery Tea Expansion

Ah right, thanks. Did actually come across that site the other day, not too sure how though now I think it was probably the Shorten URLs extension that did it.

Will look into that package, sounds interesting.

Best wishes,

Mark

Great extension, use it on all my sites - but I do get the occasional css z-index conflict in Firefox on a few fields (such as Mark Huot’s File extension) in an entry where the Edit menu will fall behind other controls on the Edit page.

So, I have changed the following line (148):-

$menu = '<ul id="publishdropmenu">';

to

to force the edit menu to stay on top.

Perhaps this could be made a [optional] setting?

So, found a bug with this great plugin. And I also figured out how to fix it.

I am not using the FTE and thus got a funny error on my Custom Fields page. CP Home › Admin › Weblog Administration › Field Groups › Custom Fields

Instead of listing my custom fields of a custom field group, it listed all my weblogs in the field label column - over and over again for each field label. It even replaces the text “Field Order” with my weblogs.

I commented out line 165 that does the extra pre_replace for FTE and it works for me.

Took me a while to track it down, but I tested this on my production server with a fresh install and it being the only extension as well as my live site with many extensions. The fix worked universally. I guess it’s not really a problem if you add this extension last after you are done creating all your custom fields. The only thing that’s getting changed is the text and link. Nothing in the DB.

I commented out line 165 that does the extra pre_replace for FTE and it works for me.

yep, doing that fixed another bug for me too - it was replacing all the entry titles in my list of items in the Simple Commerce module with the edit menu links…

Hi all,

I have removed the new 1.1 version for now because it doesn’t work as advertised on non FT-E installs.

Also Paul mentioned the following in this thread. “Already modified FT-E so that it has the Edit Menu by default. Will be in there whenever I release a new version”

If someone really needs this extension to work TODAY with FT-E 1.1.0 beta (it works fine with version 1.0) send me a PM.

Great extension!

Only problem is that when a user changes his/her localization setting to other than default language English then the Edit menu is disabled.

Is it supposed to be work like this?

The extension should work with all languages…

What version / build of the extension are you using?

I have downloaded from a link on top of this thread. Here is my current version:

Edit Menu (v.1.0.2) build: 20080704

Thanks.

Well, I think I have found the problem.

The CP English menu word “Edit” must be hard coded somewhere since when I revert that word back from local to English in the language files, it seems to work fine even in local mode.

I hope you can fix that for other language users.

The CP English menu word “Edit” must be hard coded somewhere

Nope, it’s not hardcoded.

I am about to set off for a vacation but I’ll look into a solution when I get back in about 10 days.

(I have to confess I’m still on v1.0 here, but I presume since I don’t see this mentioned here or in the change log that it hasn’t been addressed. Forgive me if it has!)

I’ve found that this Edit menu extension conflicts with the Textile Editor Helper (TEH) extension in a very minor way:

If you have dropdown long enough to overlap the textarea where your Textile buttons are, the Textile buttons appear over the top of the dropdown, giving the effect that one of your dropdown list items (weblogs) disappears from the list.

Seems to be a z-index problem - I tested adding z-index = 1 to the drop down element with Firebug, and sure enough, they now appear over the top of the Textile buttons. This is the CSS code that worked for me:

html > body #publishdropmenu, html > body #publishdropmenu * {z-index: 1;}

It would be fab if you could add this into the CSS for the next release of this extension, as I don’t know how to edit the control panel CSS without hacking into it or your extension.

Fabulous extension btw, couldn’t live without it!