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

Hi,

My clients decided to jump Joomla! versions without consulting with us, and I am also suffering from this:

Multiple primary key defined SQL=ALTER TABLE `#__flexicontent_fields_item_relations` ADD INDEX value_integer(`value_integer`), ADD INDEX value_decimal(`value_decimal`), ADD INDEX value_datetime(`value_datetime`), ADD PRIMARY KEY(`field_id`, `item_id`, `valueorder`, `suborder`)

Here is the table:



I have tried deleting primary keys or just one - but that just kills the content.

If I click on an item - I get the following:

Hello

that is not 3.1.0-rc2 , it is the new FLEXIcontent version

Still this should not be happening

Please send Joomla super-admin access
and phpmyadmin access

Sorry - I misread your instructions.

I needed to do this:

Hello

yes , do what you show in the picture, delete the PRIMARY KEY INDEX of the table

but also delete INDEXES:
- value_integer
- value_decimal
- value_datetime
- value_integer_2

and then relogin to backend and visit FLEXIcontent dashboard

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