jamesewelch

Also, when I save my Events List widget changes, I lose the HTML template, but the template that I pasted in goes into affect.

Disabling categories fixed my problem as well.

Same problem.

Workaround posted on page 1 of this thread provides a temporary fix.

Thanks!

Same here. Confirmed it’s this plug-in. I disabled each plug-in one at a time and discovered this plug-in breaks the WP 4.0 editors.

I’m having the exact same problem. I turned off each of my plug-ins to figure out which one was causing my text editor to break. After turning off the “Comprehensive Google Map Plugin,” my text editor worked fine. Then after turning “Comprehensive Google Map Plugin” back on, it promptly broke again.

This plug-in is not compatible with WP 4.0 and breaks the text editor.

The Visual Editor still works fine, but the toolbars on the text editor along with Upload Media (and other buttons) do not function when this plug-in is enabled.

Thanks. I turned off my plug-ins one at a time and checked the editor. It appears that “Comprehensive Google Map Plugin” is breaking the text editor.

Also, the Upload Media button isn’t working in either visual or text editors.

I don’t work for iThemes or JetPack, but make sure you don’t have the XML-RPC option disabled. There’s a checkbox in the Settings tab. JetPack uses XML-RPC to communicate with your blog, so if that’s disabled then you’ll probably get errors with JetPack.

In a properly set up site,
https://example.com/xmlrpc.php should show “XML-RPC server accepts POST requests only.” and https://example.com/xmlrpc.php?rsd should show some XML

In a misconfigured site, both URLs will show “XML-RPC server accepts POST requests only.”

I’m getting them same error when I use the “Press This” scriptlet.

Here’s how I fixed it. This only applies to people who have enabled “hide backend” option of the plugin and are now unable to log into their web sites.

If using FTP client
1. Use FTP to log into /wp-content/plugins
2. Rename “better-wp-security” to a different name
3. Log into wordpress using /wp-admin (it may take a few seconds)
4. I used Adminer plugin to query/access my db
5. Select the “wp_options” table
6. Filter using ‘select’ where ‘option_name’ ‘=’ ‘itsec_hide_backend’
7. Select and Delete that single row, this will reset that option and disable the hide backend option
8. Rename the plug-in back to original name

If you have access to a database query/editor via host control panel or other means
1. Delete the hide backend option, so that it becomes disabled by default:
Delete from wp_options where option_name = ‘itsec_hide_backend’

Same problem here too.

I used the “Hide backend/login” option and I see the login form on the new login page, but once I submit my credentials, I’m redirected to the old admin page which displays a 404.

I’m also never actually logged in, since I don’t see the admin toolbar on my site after logging in.

Is there a way I can turn this off via FTP without deleting the entire plugin?

Thanks. Looks like I can’t use Photon then. If I have to generate new slugs for each entry each time I need to change an image, then search engine referrals will result in 404s. I was lucky to change this slug (the entry’s name was actually changed), but I’ll still get 404s. I can’t really do that for all future changes.

Adding a button to the wp admin to invalidate the cache for a site, would be very useful. Please consider some sort of invalidation routine either site wide or for specific images. Or possibly allow an option for a time expired cache (24 hrs, 48 hrs, etc.).

Thanks for the response. The filenames are renamed by the Connections plug-in so I have no control over the names. Connections plug-in renames the images to match the entry’s slug, converts the image to JPG, and does resizing of uploaded images.

Maybe there should be a disclaimer that Photon doesn’t work with certain plug-ins?

Also, that URL above was an example URL, not my actual URL which I was having problems with. I fixed the problem by deleting the entry to create a new/different entry slug and then uploaded the logo, which was renamed to the new entry’s slug.

Thanks. I ended up editing the post-status value in the table and setting it to publish. That worked and didn’t send the email.

I’ll try that method next time, I just didn’t want to lose my existing subscribers by deactivating it.

The google+ button has never worked for me either. With no pop-up and no ads blocking extensions enabled, there’s no hyperlink for the Google+ button when I use Google Chrome.