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.
02/05/2018 at 1:05 pm #450128Steven KassGuestThis reply has been marked as private.02/05/2018 at 1:43 pm #450141Steven ZahmKeymaster
I’ve manually trigger the proper db upgrade processes. You should be good to go now. The source of the issue is that the plugin files were newer than the database structure. Whatever method that was used to upgrade the plugin files did not trigger the db upgrade routine … you would see an admin notice when trying to visit one of the Connections admin pages notifying to proceed with the database update. When you used AIO WP Migration it moved the out of data database with the current plugin file. I probably worked just fine.
My thought is the disconnect started with the dev site. How was it created? Was it pulled from the live site then changes done before being pushed back to live? Or, was it an existing dev site which happened to have an older version of the Connections tables where the plugin file were updated to the current release and then push live?02/05/2018 at 10:19 pm #450196Steven KassGuest
Thank you Steven! This is perfect! All is working now thanks again.
I do believe the disconnect started with the original dev site. The subdomain really caused a lot of problems from the start regardless – so I believe that could have caused an issue as well. The dev site did have an updated version of the plugin installed, but we could not easily import all the users through the plugin; so we did it manually through phpmyadmin. But I see what you’re saying: the data from the OLD site was from a previous version (years ago) of the connections plugin, and that is why it didn’t work. When we matched up the table names, and the items in the directory all appeared, we assumed that editing them would work too – but that wasn’t the case. Thank you again for straightening that out!
-Steven Kass02/06/2018 at 8:38 am #450257Steven ZahmKeymaster
RE: When we matched up the table names, and the items in the directory all appeared
Yeah, the actual number of tables and their names have not changed in quite a long time. The core entry table and the addresses table has had columns added. So basically when I get one of these support forum help requests, I log in to their site, see which table columns are missing and set the db version to one version less than when the missing column was added. That triggers the upgrade routine and all is well. It’s a simple fix but would be hard to walk someone thru.
Hope that helps!
You cannot reply to this support topic. Please open your own support topic.