Support » Plugin: Connections Business Directory » Export entries completely

  • Resolved msummers


    I am rebuilding a site which has about 200 entries in the Connections database. These are all Individuals with names, phone #s, addresses, city, state, category, and emails. I would like to duplicate that entire collection of data in the new site that I am developing. I am able to use either a CSV file for this or a SQL dump. Which is better? Also, I’ve tried using the Export All tool, but for some reason the categories didn’t transfer when I imported the CSV into the dev site.

    I also have another question – in the event that I want to DELETE all of the Connection data from the dev site and start Connections again from scratch, what is the best way to do that?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Steven


    Sorry to hear you had trouble with exporting/importing your directory! I don;t think I’ve ever encountered an issue where the categories were not properly migrated.

    Question, of the categories not migrated, were those categories attached to at least one entry? If they were not, then I could see them not being exported. In that case, I would recommend exporting the categories using the free export tools first and then importing them into the new site. Only the category export/import tools will transfer categories which have not been attached to any entries. I hope that is clear and makes sense!

    As for the preferred method, I prefer doing it via SQL dumps. Here’s the steps I do:

    To start, Connections should not be installed on the destination site. If you have installed it, uninstall it and then use phpMyAdmin to drop the {wpdb_prefix}connections* from the WordPress database. There are 13 of them.

    First, go to the Connections Tools admin page and export the settings.

    Now, login into the source site and go to the Connections Settings admin page. Disable the FULLTEXT search option

    Next, log into the source site’s phpMyAdmin and export those 13 tables as a SQL file. Use the quick export or default export options. I forget what the exact terminology is.

    Log into the destination site phpMyAdmin and import that SQL file.

    After the import is complete, you will need to change the wpdb_prefix of the imported table to match the wpdb_prefix of the destination site.

    Now, log into the source site via FTP and navigate to the ../wp-content/uploads/ folder. You will find a folder named connections-images. Download that entire folder.

    Next log into the destination site via FTP and navigate ../wp-content/uploads/ and upload the connections-images you just downloaded.

    Now you can install and activate Connections on the destination site.

    Import the settings on the Connections Tools admin page.

    Lastly, toggle the FULLTEXT option on the Connections Settings admin page under the Search tab. Do this by disabling it and saving the setting, then enabling it and saving the setting. This will ensure the FULLTEXT indexes are created if the db supports it.

    It sounds like a lot but it actually pretty quick with most time spent on logging in and out of the various part of the two sites.

    As for bulk delete, if you’re comfortable working directly with the database, just do a truncate on all the {wpdb_prefix}connections* tables.

    I hope this helps, please let me know.

    Thanks – this is very helpful!

    One observation from my thrashing before you replied – I was thinking that maybe the categories weren’t imported because they weren’t already defined, so I exported just the categories from the live site and tried to import them. When I browse to and find the exported categories file, I can select it, but the Upload button never really highlights. I can click it, but when I do, nothing happens – no confirmation, no screen change, nothing. What am I missing here?

    Plugin Author Steven



    Sound like perhaps another plugin is causing a fatal javascript error in the admin. This can happen when another plugin does not take care to limit their javascript files to their admin pages.

    If you can share a link to your category CSV export. I can take a look to see if I can replicate the issues on my test sites.

    Yes, I can do that. Is there a way to make it private?

    Plugin Author Steven



    No in the support forums. It sounds like you might have made a purchase of a Connections addon, the CSV Import addon. If that is the ase, you can open a support ticket and attached files and such privately.

    Here’s the link to submit a support ticket:

    You will have to login using the logins details you provided at time of purchase. I will be offline for the next 3-5 hours but I will reply asap when I get back into the office.

    I did purchase the CSV import tool several years ago, but I don’t think I have the email from that purchase any longer. If the SQL steps that you list above will take care of the problem without having to use the exported CSV files, then I’m not going to worry about it.

    Plugin Author Steven



    yeah, ok, if the CSV Import version you have is from yeas ago… much has changed so I guess there is potential for it not to import data correctly from the current versions export. I would suggest doing the SQL migration since it sounds like it you might have some experience with doing that. When I migrate directories for users, that is the method I personally use since it is quicker for me.

    Yeah – I though that should work. I’ll give that the first try. And yes, I’m pretty comfortable working at that level.

    Regarding the FULLTEXT search option that I disable in the source site – should I re-enable it after exporting the tables?

    Plugin Author Steven


    Yes, I recommend enabling at the destination site, after import. The reason for turning off, then back on is I’ve found that depending on the default config for mysql could cause the import to fail if the FULLTEXT indexes are included in the exported SQL file. It is fine to leave on if importing to a different site on the same host (from my experience).

    And I should re-enable it on the source site too, right?’

    Other than this, the SQL process worked PERFECTLY! Thank you so much.

    Plugin Author Steven


    Yes, you should enable it on the source site too if you plan on keep it around:)

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.