Hi all,

I just released a new extension: Editor

Here’s what it does:

Editor adds little Edit buttons next to each of your entries, right on your website. Click on one of them, and that entry’s Edit page will open in a new window.

Enjoy!

Brilliant!  I too have issues with the workflow involved in editing an entry.  I usually add links for site administrators and content editors to edit the content from the frontend as well.  Except, I don’t do it all fancy-like with an extension.  Hopefully, I won’t have to manage all those links now.

I haven’t yet downloaded it, but let me ask a question first anyway.  For whom do the links show up for?  For superadmins only?  Is there a setting to set which member groups can see the link?

Again, great work.  And cool new site design

Arun S. - 05 January 2009 08:16 AM

For whom do the links show up for?  For superadmins only?  Is there a setting to set which member groups can see the link?

They show up for anyone that’s logged in and has Edit permissions. It doesn’t factor in whether they are allowed to edit that weblog (yet).

I love this idea! I’ve been using Ryan Irelan’s edit button technique, but this is far superior if i can get it to work. So far, i see no edit icons. Does it only work in a certain implementation style?

Jack McDade - 05 January 2009 11:02 AM

I love this idea! I’ve been using Ryan Irelan’s edit button technique, but this is far superior if i can get it to work. So far, i see no edit icons. Does it only work in a certain implementation style?

Can you search the HTML source for “editor-button” ?

Most likely they are getting added, but the default CSS is putting them in a place where you can’t see them.

Which brings up a good point: The default CSS for these is only going to work in most situations. You may need to override it. Here’s one example, if the {exp:weblog:entries} tag is creating inline text nodes or something:

Another common example would be that your {exp:weblog:entries} tag starts at the very left of the page, so the buttons are actually getting pushed out of sight. For that you could try:

Brandon Kelly - 05 January 2009 11:13 AM

Most likely they are getting added, but the default CSS is putting them in a place where you can’t see them.

That was it! The non-rollover state was actually too faded to see against my white background. Easily remedied! Nice work! Wish i thought of this first lol

Now to further mod and add a New Entry button as well…

Jack McDade - 05 January 2009 11:20 AM

That was it! The non-rollover state was actually too faded to see against my white background. Easily remedied! Nice work! Wish i thought of this first lol

Now to further mod and add a New Entry button as well…

Haha, you can take that one!

Fantastic, Brandon. Next bit of money that comes my way, you’ll get some.

Brandon,

When I add the url to the system index page I get the following error:

Notice: Undefined index: check_for_extension_updates in /path/to/system/extensions/ext.editor.php on line 303

Warning: Cannot modify header information - headers already sent by (output started at /path/to/system/extensions/ext.editor.php:303) in /path/to/system/core/core.functions.php on line 296

love the idea behind this but am unable to get it to work on www.davidould.net

It shows up in the source but won’t show up on the page! Have tried the fixes above but to no avail.

Any suggestions?

[deleted] Was accidentally using 1.0.1. Problem fixed by updating to 1.0.2.

Great! This is very helpful.

Sean C. Smith - 05 January 2009 03:53 PM

When I add the url to the system index page I get the following error:

Notice: Undefined index: check_for_extension_updates in /path/to/system/extensions/ext.editor.php on line 303

Warning: Cannot modify header information - headers already sent by (output started at /path/to/system/extensions/ext.editor.php:303) in /path/to/system/core/core.functions.php on line 296

Make sure you’re using v 1.0.2 and you’ve saved your settings.

David Ould - 10 January 2009 02:42 AM

love the idea behind this but am unable to get it to work on www.davidould.net

It shows up in the source but won’t show up on the page! Have tried the fixes above but to no avail.

Any suggestions?

See Post #4 above.

Brandon Kelly - 11 January 2009 02:50 PM

Sean C. Smith - 05 January 2009 03:53 PM

When I add the url to the system index page I get the following error:

Notice: Undefined index: check_for_extension_updates in /path/to/system/extensions/ext.editor.php on line 303

Warning: Cannot modify header information - headers already sent by (output started at /path/to/system/extensions/ext.editor.php:303) in /path/to/system/core/core.functions.php on line 296

Make sure you’re using v 1.0.2 and you’ve saved your settings.

upgraded to 1.0.2 and when I try to save my settings I get the same error.

I’ve tried it on a fresh install with no other extensions as well as a productin site.

Any issue using this extension with the Multi Site Manager?  I’m not seeing the edit buttons on pages or source code, and I’ve quadruple-checked that the CP URL is set correctly in the Editor extension settings.  Would love to get this working!

Thanks,
Jack

Have just installed this extension and it works, however I’ve got a major glitch.

I use the weblog entry tag to display entry title in my URL and that’s where the edit button is appearing, not in the body.

Any ideas?

I’ve installed this and it works great. The one problem is that I am using a template to output a link list for tinymce in expressionengine and now I am getting js errors because editor is trying to add buttons to the list. Is there a way to turn off editor for a template or is there some other way to output entries that by-pass editor?

Thanks.

OK I didn’t think I was this dumb but apparently… I’m seeing the editor-button div in the source code, but can’t seem to tweak the CSS to make it visible.  Here’s what I see in the source:

This appears just before the weblog entry.  (BTW, as Steven mentions two posts back, it was appearing in my Title tag in the head section before, as I was also putting the entry title there using weblog tags.  That’s a separate issue I think.)

I’m not sure why the css for editor-button would follow the html for it.  Shouldn’t that be…elsewhere?

I’d love to get this working!

Here’s the page from which I grabbed the source code: http://www.pbcoreresources.org/article/index2/story-related_images_wtf/