WIBeditor

I’m building a buddypress site with this plugin. It does seem to generate a lot of queries on the homepage, where I’m not (intentionally) loading GMW maps or search functions. I wish there were an option to disable GMW completely for certain post types or pages. Until then, I’m open to suggestions…

I just reproduced the issue with a fresh cache and with the logged-in user cache enabled. I visited multiple pages with different accounts in different browsers. The new cached version of the page shows the admin bar of the first user to visit after the cache was cleared. Maybe this is expected behavior? I’ve disabled the logged-in user cache for now.

I ran into this issue on my local development virtual machine. @carterconnection21’s approach worked. But CURL works as normal on my staging server, so I assume it’ll work in production. Not sure what the problem was with the dev server… but I’m sure other people are likely to run into this issue as well.

You might consider patching in this code with an advanced option in plugin settings to toggle the “alternate Google Maps geocoding method,” or something like that.

I appreciate that you’re trying to keep it constructive, and I know developers get an unfair amount of grief around here. But whatever the precise nature of the interaction, the proximate cause of the admin lockout was definitely the plugin. I thought I’d give this plugin a try before attempting to code my own solution, and the consequences were ugly. So you understand the impulse, I’m sure. Still, point taken.

Thanks!

Ditto. Same problem, same version, same timeframe. Except I’m not using buddypress.

See #360
https://planetozh.com/blog/my-projects/yourls-wordpress-to-twitter-a-short-url-plugin/?cp=36#comments
and #363

I’m getting this too, with YOURLS install and bit.ly. Not every time—seems random. Thought it might’ve been something to do with the custom field settings, but it still happens when I auto-Tweet using the built-in %T and %U parameters.

I’m using WP 3.05 and YOURLS 1.4.9.

Works! Cheers.

Awesome, thanks—I’ll check it out now.

I had this same issue with broken permalinks for custom taxonomies after a host migration. I narrowed it down to the plugin, because the default tag and category permalinks continued to work just fine.

Thanks for the posting the fix—it all works now. You might want to copy it to the plugin page, where it’d be easier to find.

Cheers.