Jump to content
thirty bees forum
  • 0

Core update says critical


Question

6 answers to this question

Recommended Posts

  • 0
Posted

Backup your DB and apply all of them. Nothing should change in your FO or BO. One (or few of them) may not get fixed with the button because of bug in the module which was identified and will be fixed in the next release. You can find my thread in the forum with the same question and the solution to this issue.

 

  • 0
Posted

Yes, I found out that if you make 2 instances in 2 windows side by side and start from different points in the list it's nearly twice faster. No automated way to apply all of them currently and probably there won't be one as some fixes rely on other to complete.

30 minutes - 1 hour of 'work' for 1000 fixes.

  • 0
Posted

Very highly doubt this is related.

As I advised you should have created backup of your DB. Now after the fixes - create backup of the after situation and restore your old one to check if this spinning button is fixed. If not you can restore the after situation and continue with the fixes while you search for solution to this issue.

  • 0
Posted

I don't think this is related. You should look to server log for any errors. Also check browser console network tab and look into ajax response content -- there are often some helpful information there.

Also, don't forget to turn on debug mode in Advanced parameters > Performance. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...