infoxicated

Yep, I’m getting this too with the Updraft Plus plugin suite I just bought – the support guys have never seen this error before, so there has to be something causing it in the new WordPress core.

Will do.

Was there ever a resolution for this?

I’m getting similar issues with weird characters appearing in the dumped text. The db collation is UTF8_unicode_ci.

Hi mitcho – thanks for getting back on this, sorry I haven’t seen your post until now.

The stage server is updated with a dump from the local database, so all the tables are replicated from a phpMyAdmin db dump with MyISAM and utf8_general_ci collation.

It’s a strange one – all of the other plugins retain their settings.

Sorry I missed this – the problem is we haven’t got it working, we just have to manually go into the settings for YARPP each time we deploy the content to our stage server.

It’s inconvenient, but for now we’ll have to do that to ensure the settings are correct.

No, it doesn’t seem to make a difference.

For now we’ve made a note on our Trello board that the YARPP plugin needs to be manually configured on each environment. It’s not ideal, but we can live with it until we get a better understanding of what’s causing it.

I’m experiencing the same problem – YARPP is set up and works fine on local development server, but when we migrate to stage all the settings are lost and we need to manually set the plugin up again.

Thanks for your response, Mika – it’s a shame there isn’t a way around this. I think what I’ll have to do is just stage it in English only then perform a site move operation when it comes time to make it live, then set up the multisite configuration.

I had the same problem this morning. Despite being on WordPress 3.4, when I clicked on the URL to link the two accounts it would not work.

Out of curiosity I logged into my dashboard using IE instead of Chrome and it turned out that Chrome had been blocking the authorisation pop-up that appeared when I clicked the link in IE.

Hope that helps some people. ??