Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
- This topic has 4 replies, 2 voices, and was last updated 11 years, 5 months ago by
Steven Zahm.
-
AuthorPosts
-
03/04/2015 at 11:32 am #321516
Charles McPadden
ParticipantThis morning I upgraded to Connections 8.2.1. The update appears to have worked, however, during the upgrade process I received several database errors. Please see the attached screen shot.
Attachments:
You must be logged in to view attached files.03/04/2015 at 12:19 pm #321540Steven Zahm
Keymaster@ Charles
No worries here, those are simply informational notices created by WordPress. The DB table engine for the tables used Connections do not support FULLTEXT search indexes. Connection will fallback to a simpler/less accurate search routine in this case.
My guess why you’re, specifically, saw these notices during the update is that you have an older install of Connections … older meaning initially installed a year or two ago. Newer installs, this is properly detected at the initial install and will create the tables with the correct table engine to support FULLTEXT indexes. Older installs, when the tables were created, it just used whatever default table db engine the web host defined as the default.
Any way… probably more than you wanted to know, but I hope it helps.
03/04/2015 at 12:20 pm #321541Keymaster@ Charles
Oh… I should add things will work the way they always have for you.
03/05/2015 at 11:07 am #321742Keymaster@ Charles
Please do not reply to the auto replies, I typically do not even see them… thanks!
Steven,
Thank you for the detailed response. Yes, my install is about a year
old. Just for my own understanding, is there something I need to do in
order to get the FULLTEXT index support? I would like for my software
and database to be as current as possible.Thanks in advance. Charles
03/05/2015 at 11:15 am #321745Keymaster@ Charles
You could use phpMyAdmin or similar tool to change the table engine to one that does support FULLTEXT.
This post may or may not help:
http://rdeshapriya.com/fulltext-mysql/My guess is the host is on an older version of MySQL and the default table type is InnoDB. IF, that is the case then you need to change the engine type for all the Connections tables in the DB to MyISAM.
If you decide to do this, backup the db first in case something goes wrong. And after you change the table engine, go to the Connections : Settings admin page and ensure the FULLTEXT option is enabled under the Search tab. Whether or not you have to change this settings you will have to click the SAve Changes button so the indexes are created.
Hope that helps.
-
AuthorPosts
You cannot reply to this support topic. Please open your own support topic.