WordPress caught an error with one of your plugins, Auto Image Attributes From

Hello @harry56789

My name is Arun. I tried to look into the file and see if I can recreate the error, but I can’t. Something seems to be off.

Let’s first fix the login issue and then look into figuring out the issue for you.

Do you have access to the WordPress files via FTP? Maybe in the cPanel? If so, navigate to \wp-content\plugins and rename the folder auto-image-attributes-from-filename-with-bulk-updater into something else temporarily.

Then access the WordPress dashboard. WordPress will now disable the plugin and allow you to login.

Once you are in, uninstall the plugin and install the plugin again. Activate the plugin and see if the error persists.

I will be here waiting for your feedback. Please let me know.

Hello again @harry56789

I have found the issue and I am releasing an update with the fix right now. I will explain what happened afterwards. Sorry for the panic and trouble.

Hello @harry56789

I have just released 4.3.1 that will fix this issue. The error was caused because a feature I used is not available in PHP versions older than 7.3.

I have added a test routine and I will test future releases with PHP 5.x to catch such issues early. Sorry about this time and thanks for reporting.

You can download version 4.3.1 directly here: https://downloads.www.ads-software.com/plugin/auto-image-attributes-from-filename-with-bulk-updater.4.3.1.zip

I sincerely hope that helps. Please let me know if you were able to figure it out or if you need further help.

I think there is another bug. I updated to 4.3.1 and the plugin remains at 4.3.0. I tried to update many times.

Hello @buzucan

It’s a cache issue on the wp.org repo I think. I had this before and it cleared up after an hour or so – https://www.ads-software.com/support/topic/ver-4-0-svn-out-of-sync/

Please download 4.3.1 directly for now – https://downloads.www.ads-software.com/plugin/auto-image-attributes-from-filename-with-bulk-updater.4.3.1.zip

Thanks ??

I have installed 4.3.1 and it seems to have fixed the issue. Thanks.

Thanks for reporting back @harry56789, glad to hear that ??