tamlyn

Hi Jacob, were you pulling or pushing when you got this error? And are you also using Hostgator?

Yes, the change will persist if you deactivate or uninstall the plugin.

Could you try the latest version and see if it fixes your issue?

Nice one. I’ve applied your improvements and released a new version. The code is now on GitHub so you can direct any future contributions there: https://github.com/tamlyn/unattach

Thanks! Done.

When the plugin is activated it generates a 16 character random string (~104 bits of entropy) using mt_rand(). This key is stored in the options table as outlandish_sync_secret. The token is generated by concatenating this random string with the site URL and base 64 encoding the lot.

When you copy and paste the token to another WordPress installation, it decodes it and stores the secret key and remote URL in its options table. When doing a pull or a push, the key is POSTed (in plain text) to the remote server and compared with the key stored there.

The mechanism is essentially the same as most login forms on the internet, although the password is considerably harder to guess than anything a human could memorise!

I hope this explains things and sorry for not responding sooner. I’ll add something along these lines to the FAQ.

There is no comparison of the data, it’s a straight overwrite from one server to the other (depending which way you are syncing).

This could indeed be explained more clearly. I will improve the description in an upcoming release.

I believe this (paid for) plugin may do what you want: https://crowdfavorite.com/ramp/

The remote SQL options should not be required as the database is accessed locally at each end and communication is plugin to plugin over HTTP.

Did you make any progress with this?

It should currently copy all tables from the database, not just those with the wp_ prefix. I’ve not tested it with WooCommerce but I use it with ACF all the time.

Thanks for the kind words. I’m hoping to have a bit more time to develop this plugin further in the coming months. Development is happening on GitHub so feel free to file bugs, feature requests or contributions there https://github.com/tamlyn/database-sync

Please try the latest version 0.3 which fixes this problem. Thanks to Simon East for the patch.

Sorry it didn’t work for you. Could you email me the errors and maybe the output of phpinfo() too? I’ll see if I can track down the problem. My address is <username>@<username>.org

Thanks. We use it every day here at Outlandish Ideas but it hasn’t been tested widely in the field on different servers so we still consider it beta quality. To the best of my knowledge it is secure but for extra peace of mind, probably best to disable it on production servers.

Here’s my solution: everything works after upgrading WPSEO to 1.2.5 with strip category base checked UNTIL I flush the permalinks by visiting Settings > Permalinks. To reverse this, I can uncheck strip category base, flush permalinks again, then re-enable strip permalinks. However be careful because flushing permalinks breaks it again.

Hopefully this will be fixed soon. It’s kinda ironic that this SEO plugin is resulting in sites being banned from Google!

Scratch that, turns out you can pass post_type=any to WP_Query.

I wrote the Unattach plugin but I’ve since given up trying to use the built-in gallery.

I find that Advanced Custom Fields (free) with the Repeater Add-on ($25 for multi-site) makes excellent image galleries that clients find easy to update. I really can’t recommend ACF enough.