We have received the same error which took down the site completely. When I removed your plugin the site works again. Can you please let us know when you get this fixed so that we can reinstall latest plugin update. Thanks!
I solved this issue by copying some lines in class-xmlsitemapfeed-admin.php of version 4.7.5 to the installed file of version 4.8.2.
Afterwards line 632 and 633 read:
$genres = !empty($options[‘genres’]) ? $options[‘genres’] : array();
$genres_default = !empty($genres[‘default’]) ? (array)$genres[‘default’] : array();
And line 655:
$keywords = !empty($options[‘keywords’]) ? $options[‘keywords’] : array();
is the vendor going to update the plugin? I don’t like to tweak code of someone else’s plugin.
The version 4.8.2 has been published about 21 hours ago.
I hope the plugin author would read here, too.
My solution should help until the author would release a new verion.
If they do, I guess I’ll have to FTP the changed files as I can not access the admin area of my site.
You can rename the plugin directory by (s)FTP. By doing this, the plugin is deactivated and you are able to access the WP backend again
Thank you GuentherLudwig for your help!!
Hi all, the issue here is an outdated PHP version. Anything under 5.4 will suffer this problem. My recommendation is to upgrade your PHP version (or contact your provider) as soon as possible to at least version 5.6 that is still receiving security updates till the end of the year, but better to PHP 7.0 or higher as recommended by WordPress.
Running such an old PHP version is putting your site at risk.
That said, I’ll apply the backward compatibility fix suggested above in the upcoming release so if you really cannot upgrade PHP, you should be able to continue with the plugin.
Thank you RavanH! I will work on upgrading the PHP that I am using, your compatibility fix will help until I can upgrade one other shopping cart that I am using on the same hosting account.
Thank you RavanH. Will you please notify us via this thread when the fix has been applied to the upcoming release? Thanks! I’ve uninstalled the plugin til we get that fix.
Just released 4.8.3 which has this fix 🙂
