After upgrading Joomla to 3.5 and Flexicontent to 3.0.14 I receive error when attempting to browse to flexicontent menus in the backend. Error gives message that there is an error on the database which I have run repairs on through phpmyadmin with no luck.
Looks like the database has issues however it is not full at 57% of its capacity. Can you please advise if there is anything that can be done please?
Code:
1267 Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' SQL=SELECT COUNT(*) AS total1, ( SELECT COUNT(*) FROM `#__flexicontent_items_ext` AS ie JOIN `#__content` AS i ON ie.item_id=i.id WHERE 1 ) AS total2 FROM `#__content` AS i JOIN `#__flexicontent_items_tmp` AS ca ON i.id=ca.id JOIN `#__flexicontent_items_ext` AS ie ON ie.item_id=i.id WHERE 1 AND i.`title`=ca.`title` AND i.`state`=ca.`state` AND i.`catid`=ca.`catid` AND i.`created`=ca.`created` AND i.`created_by`=ca.`created_by` AND i.`modified`=ca.`modified` AND i.`modified_by`=ca.`modified_by` AND i.`publish_up`=ca.`publish_up` AND i.`publish_down`=ca.`publish_down` AND i.`version`=ca.`version` AND i.`ordering`=ca.`ordering` AND i.`access`=ca.`access` AND i.`featured`=ca.`featured` AND i.`language`=ca.`language` AND ie.`type_id`=ca.`type_id` AND ie.`lang_parent_id`=ca.`lang_parent_id`
Joomla 3.5.0 improves support for Unicode and changes collations of Database table to:
utf8_unicode_ci or utf8mb4_unicode_ci
this has been reported by other people, please search forum before posting
- we have already made new package (v3.0.14-rc2a) , test it and report back if you still have an issue
-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the
FLEXIcontent JED listing
with a 5-star...
George, very sorry that I didn't find the previous threads, I did look but maybe did't recognise my issue, I was upgrading multiple sites and one of the sites came up with this error, the others didn't and they are on the same host.
Thanks very much for a quick response and the application is going from strength to strength, thanks for the hours / days that you are investing.
