Alexander Celeste

I’ll post a support request there, but I want to emphasize that this only started with this free plugin’s update, and so should be something this free and public support forum can help figure out. So at minimum it was good to post here so others who may have similar issues see it.

Any updates on the status of this getting back? I’m ready to replace with Safe SVG, but won’t if I don’t have to.

Oh great… Well, at least we know it is a safe enough update. But still… Speaking as a plugin dev myself, folks can update the tested up to without bumping plugin version numbers. I do it all the time. Like, literally, never have I had to update a plugin for feature changes or bugfixes alongside bumping the tested up to number. So, nice to know, but an annoying habit of this developer.

Fixed for me.

The 1.9.15.1 update isn’t showing up yet.

I’ve seen the same thing. This really needs to be resolved ASAP. I had to downgrade my test site and will not be updating any of my live sites to this version.

There weren’t any javascript or PHP errors appearing in logs that I could find. This makes me wonder exactly what javascript could get in the way, when the javascript console showed no errors.

I tried on a blank WP install, and as you expected, that did work. The interesting thing is that I could then copy the photonic_options row from the blank WP’s options table to the live one, and all stayed in place, including doing the authentication step on the live site and the plugin could then save the refresh token for itself.

So perhaps something is awry with your plugin’s compatibility with something else on my site, but at least I could use a blank Local WP install as a workaround to get it to work.

@howdy_mcgee thanks for the clarification.

I’m still seeing the same issue with the current version of WooCommerce.

I don’t like to edit other people’s plugins when used on production environments, but what I found to work in a staging environment was not what @howdy_mcgee exactly said. That is, there is nothing around line 207 that makes sense to add this in near, as that file has a class near there. What worked for me was to just append the code block above at the end of the file.

@robscott what version is current, though? My sites that I use this on all have 1.7.1 with not being able to update further in any way, but I see in the changelog there is a 1.7.2. On the command line, when I try to reinstall the plugin with wp-cli, it complains of an inability to verify 1.7.2, and I guess just reinstalls 1.7.1. Maybe may server is somehow stuck at assuming 1.7.1 is current, and that is the heart of line numbering differences?

@robscott, it is possible that I once opened the plugin file, which may have then formatted it with my code editor. I definitely haven’t intentionally edited the plugin. It isn’t asking for an update, so I’m running the latest version. That is fine. If the error is the same, then it should be fixed in a later release regardless.

I’m seeing a similar warning:

PHP Deprecated:  Invalid characters passed for attempted conversion, these have been ignored in /plugins/mailgun/includes/wp-mail-api.php on line 332

Same file, but different line.

• This reply was modified 3 years, 9 months ago by Alexander Celeste.