CarstenTimm

I bought a new licens for the pro version of the plugin

First I renamed the folders back to their original name, then I first reactivated the free plugin, then deactivated it and deleted it, I then updated the pro plugin by uploading the new version, and replaced the old version of the pro plugin.

The site woks, and I have the newest version of the pro plugin now.

I think that updating the collation algorithm was just a coincidence, well the site works now, and that is the most important!

Question:
Will the settings from the old pro version still be there, or do I need to reapply them by going through the setup again?

I will explore the new updated pro version, and see what that offers of new goodies ??

Kind regards
Carsten

Hi again @jarnovos

Yes I had both the Free and Pro plugin activated next to each other. And I am a little concerned that deactivating the pro, will cause problems with some of the security headers, but I’m not sure about that.

It was an older version of the Pro and the newest version of the free plugin

Again let me know if I should try anything to help you debug, and to help get it working again ??

Kind regards
Carsten

Hi @jarnovos

The collation algorithm has been updated to utf8mb4_unicode_520_ci across all tables in the database, to avoid mix of collation errors.
It worked without any problems on the staging site, and that site still runs without issues, so a little strange if that is the cause of the problem.

Let me know if I should try anything else?

Kind regards
Carsten

After renaming the folder for the Really simple security and the pro version, I can now login to the backend, no problem.

If I just want to remove the two plugins, is there anything I need to be aware of?

All the best
Carsten

I am experiencing the exact same problem, after the update all e-mail fields are required, even the ones that are hidden by conditional logic, that was a pain to find out, but I can now say that I have the exact same problem!

I have tried to ude conditional logic to tell the field that it is not required, on top of it beeing not required by the form settings, nothing has worked, hope that you fix this soon, as it is causing trouble for me.

Thanks

Hi Hessel

Sorry for taking my time to reply, I testet your suggestion on a staging site, and it worked, I have one follow up question for you, hope that you have time to answer ??

In the “report” generated by Database Collation Fix, after it had run, I could see that several plugins including Bürst had stored data using ‘utf8mb4_unicode_520_ci’, I’am guessing that is not something that you program the plugin to do.

Would it be an idea to update wp-config.php changing the following setting to:
define(‘DB_COLLATE’, ‘utf8mb4_unicode_ci’);

Would that stop the problem from occurring, or is it just something I need to clean up from time to time?

Can you think of any potential drawback from defining DB_COLLATE in wp-config?

Thank You ??

Sorry, this is a second post on the same problem, as I did not see that the first one was held for moderation, Sorry

Please feel free to release the one that you find best ??

Thank you very much for your answer! ??

The fix suggested by Daniel Payne worked for me, but my slider images did not look good after implementing the fix, they all got a black bar underneath.

I then downloaded the newest version of the Nivo Slider from https://nivo.dev7studios.com/ and updated the three files in the folder plugins/easy-nivo-slider/3rd-party/ – This worked great for me.

Hope that it can help others in this situation.

I had the same problem:
When I have this plugin activated in wordpress 2.9.2 wp-admin/index.php delivers an Internal Server Error

In the file “googleanalytics.php” added /* in front of line 46 and */ in the back of line 46, disabling that line of code – It now looks like this: /*add_action('wp_dashboard_setup', array(&$this,'widget_setup')); */

In the file “yst_plugin_tools.php” I also blocked out line 28 it now looks like this: /*add_action('wp_dashboard_setup', array(&$this,'widget_setup')); */

And I blocked out lines 219 to 223 in the same file, it now looks like this: `/*function widget_setup() {
$options = get_option(‘yoastdbwidget’);
if (!$options[‘removedbwidget’])
wp_add_dashboard_widget( ‘yoast_db_widget’ , ‘The Latest news from Yoast’ , array(&$this, ‘db_widget’));
}*/`

Now wp-admin/index.php works again, and the plugin works, I’am not sure if you need to block out all the lines of code that I blocked out, but I works ??

I disabled the plugin while editing the code, and activated it again after uploading the edited files.

I hope this workaround works for you also, let us know. ??

I have the same problem:
When I have this plugin activated in wordpress 2.9.2 wp-admin/index.php delivers an Internal Server Error

In the file “googleanalytics.php” added /* in front of line 46 and */ in the back of line 46, disabling that line of code – It now looks like this: /*add_action('wp_dashboard_setup', array(&$this,'widget_setup')); */

In the file “yst_plugin_tools.php” I also blocked out line 28 it now looks like this: /*add_action('wp_dashboard_setup', array(&$this,'widget_setup')); */

And I blocked out lines 219 to 223 in the same file, it now looks like this: `/*function widget_setup() {
$options = get_option(‘yoastdbwidget’);
if (!$options[‘removedbwidget’])
wp_add_dashboard_widget( ‘yoast_db_widget’ , ‘The Latest news from Yoast’ , array(&$this, ‘db_widget’));
}*/`

Now wp-admin/index.php works again, and the plugin works, I’am not sure if you need to block out all the lines of code that I blocked out, but I works ??

I disabled the plugin while editing the code, and activated it again after uploading the edited files.

I hope this workaround works for you also, let us know. ??