Title: [Plugin: Front-end Editor] A few problems
Last modified: August 19, 2016

---

# [Plugin: Front-end Editor] A few problems

 *  Resolved [Bill Dennen](https://wordpress.org/support/users/xyzzy/)
 * (@xyzzy)
 * [15 years, 7 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/)
 * Hi,
 * I am having trouble with the front-end editor. Basically, when I double-click
   on content to edit it, the NicEdit box comes up empty. Nothing in it.
 * I am running wp-admin behind SSL and thought that might be it. So, as a test,
   I set this to false.
 * define(‘FORCE_SSL_ADMIN’, false);
 * Now, when I double-click on the content, the NicEdit box is filled with simply:
 * -1
 * Clearly FORCE_SSL_ADMIN is having some effect. But, there may be something else
   going on here, too.
 * any ideas?
 * Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Thread Starter [Bill Dennen](https://wordpress.org/support/users/xyzzy/)
 * (@xyzzy)
 * [15 years, 7 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1712781)
 * I did some more digging.
 * With FORCE_SSL_ADMIN true, since this is how we want to run it.
 * URL of post = [http://somedomain.com/somesite/2010/10/test-2/](http://somedomain.com/somesite/2010/10/test-2/)
 * All of our public-facing pages are accessed over http. Backend should be https.
 * If I try to edit the content with the front-end-editor, I get the blank NicEdit
   box.
 * If I change the URL of the public page to https:
 * [https://somedomain.com/somesite/2010/10/test-2/](https://somedomain.com/somesite/2010/10/test-2/)
 * it works! Looking for suggestions.
 *  Thread Starter [Bill Dennen](https://wordpress.org/support/users/xyzzy/)
 * (@xyzzy)
 * [15 years, 7 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713044)
 * any suggestions for this? Should this plugin work with an SSL backend?
 *  Plugin Author [scribu](https://wordpress.org/support/users/scribu/)
 * (@scribu)
 * [15 years, 7 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713046)
 * It fails because it’s trying to make an ajax request to a SSL page (`wp-admin/
   admin-ajax.php`) from a regular page.
 * So, you either make the entire site SSL or tweak the ajax_url variable in the
   plugin to use the `http://` protocol.
 *  [TheRingBearer](https://wordpress.org/support/users/theringbearer/)
 * (@theringbearer)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713106)
 * scribu > Could you please detail more about tweaking the ajax_url variable ? 
   If the plugin use some php functions in wp-admin directory AND if wp-admin is
   always accessed through https, how could you make it work ?
 *  [Nyhm](https://wordpress.org/support/users/nyhm/)
 * (@nyhm)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713110)
 * [@scribu](https://wordpress.org/support/users/scribu/), Could you clarify this
   issue? If page is https, then `wp-admin/admin-ajax.php` should be over https …
   right?
 * What I’m seeing is a bunch of access logs of `wp-admin/admin-ajax.php` via **
   http** when WP admin is strictly **https**, which bothers me greatly (and causes‘
   partially encrypted content’ warnings).
 *  Plugin Author [scribu](https://wordpress.org/support/users/scribu/)
 * (@scribu)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713111)
 * To generate the ajax url, the plugin uses the admin_url() function:
 * [http://plugins.trac.wordpress.org/browser/front-end-editor/trunk/php/core.php?rev=428274#L53](http://plugins.trac.wordpress.org/browser/front-end-editor/trunk/php/core.php?rev=428274#L53)
 * which should be SSL aware:
 * [http://core.trac.wordpress.org/browser/tags/3.2.1/wp-includes/link-template.php#L2043](http://core.trac.wordpress.org/browser/tags/3.2.1/wp-includes/link-template.php#L2043)
 * I don’t know what else to tell you.
 *  [Nyhm](https://wordpress.org/support/users/nyhm/)
 * (@nyhm)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713112)
 * Yes, that’s exactly what I thought, too. I must have a plugin that is hard-coding
   the http. Thanks for your input.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘[Plugin: Front-end Editor] A few problems’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/front-end-editor.svg)
 * [Front-end Editor](https://wordpress.org/plugins/front-end-editor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/front-end-editor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/front-end-editor/)
 * [Active Topics](https://wordpress.org/support/plugin/front-end-editor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/front-end-editor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/front-end-editor/reviews/)

 * 7 replies
 * 4 participants
 * Last reply from: [Nyhm](https://wordpress.org/support/users/nyhm/)
 * Last activity: [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-a-few-problems/#post-1713112)
 * Status: resolved