[SOLVED] DB-index issues with upgrade from J2.5 / FC 2.x to J3.6 / FC3.1.0RC2

I am also have DB issues after I upgraded: I first get this:


After I update, I get this

Hello

The task has code to DROP the old PRIMARY key !

this is not happening for some reason,
would like to see why,

you may send a PM with super admin access to the website

Hello

i found that under some cases the SQL code for indexes is executed in wrong order,
to fix now in your website:

edit
administrator/components/com_flexicontent/controller.php

Find (about line 879):
And after it add:
I have added fix to our code so that it exists in our next release

Hello

@clutchmarketing
if you have applied the fix and it worked, you should post back feedback about it, that it worked

Regards

That worked perfectly. Thanks so much for your help.

Hello,

I had the very same issue.
Adding the code in controller.php solved it straightaway.

Many thanks
Antoine