phbernard

Thanks Jenna!

Thank you!

Thanks Jan-Hinrich!

Just to let you know that I investigated this feature. wp insert attachment is a good starting point. However, I currently have more questions than answers.

FYI I posted a question: http://wordpress.stackexchange.com/questions/192670/strategies-for-a-plugin-to-support-cdn-enabled-wordpress-sites

Deployed as part of v1.3.1.

Thank you very much Alexander!

To all users that have been impacted by this issue: I’m very sorry. My bad.

v1.3.0 was an important update and I refactored many things in the plugin. I spent a few hours just to make sure nothing was broken. I clearly missed the point, completely forgetting a scenario that could trigger the faulty code.

More about this issue. I analyzed it to understand its impact.
First of all, it impacted only the Dashboard part. Not the main site. In other words, even if you were stuck with a broken site, your visitors must not have noticed any problem.

The issue itself was a silly PHP syntax error: $this->get_update_data( $version )['description'] is illegal. It had to be turned into $update = $this->get_update_data( $version ); $update['description'].

This code was triggered in combination of two settings:
– There is an update notice to display (something like “A favicon update is available, you should generate your favicon again”).
– There is no update description available. This happens just after you install/update the plugin, since versions prior v1.3.0 din’t use to store descriptions.

So basically, the issue occurred on WP sites that had a pending favicon update and which got the 1.3.0 update. This update lasted 20 minutes: after this is was replaced by 1.3.1.

Hopefully only a few users were impacted… If you read this you are probably part of them, so, again, sorry for this 🙁

You’re welcome!! Thank you for letting me know and for closing the ticket.