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.
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.
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.
11/11/2015 at 5:08 pm #354618Jessica BoctorParticipant
I purchased the Pro Pack because this seemed like a really nifty plugin that I would be able to use for multiple clients. However, I have a problem with importing or exporting the MySQL database whenever I try to include the connections tables in import and export. I have wasted numerous hours trying to deploy a site from my local development to a staging site, I don’t even know what it will look like to actually deploy a live site if I use this plugin. I am attaching a zip file with screen shots of the errors I have received. Any insight you can give into why this is happening would be greatly appreciated.
Attachments:You must be logged in to view attached files.11/11/2015 at 5:50 pm #354623Steven ZahmKeymaster
Well, best guess… the version of MySQL installed in the host is outdated. What version is installed? I ask because your local install must be a more recent version because it supports InnoDB and FULLTEXT. When Connections installs it creates its custom table based on the supported features of the MySQL it is being installed on for maximum efficiency. So, this is really a server config issue, not really a Connections bug or limitation. When pushing from a local (or server to server) the software stack should be setup to be similar as possible.
You have two options…
One, update MySQL on your production server. If it is update to date enable the InnoDB engine (which is by default on install, so it would have been disabled intentionally).
Two, on your local install… go to the Connections : Settings admin page and click the search tab and disable the FULLTEXT option. Then go to phpMyADmin on you local install and change the table engine from InnoDB to MyISAM (the default table engine in older versions of MySQL).
Hope this helps! Let me know.
You cannot reply to this support topic. Please open your own support topic.