Viewing 15 replies - 1 through 15 (of 36 total)
  • Plugin Author Tijmen Smit

    (@tijmensmit)

    No the phpMyadmin trick doesn’t work anymore with v2. There are no custom tables anymore, so phpMyadmin ( or any other sql tool ) isn’t capable of handling it. But I’m working on a CSV importer add-on that will be released soon ( I probably should have had this ready when I released the 2.0 update ).

    The old table is still there though ( unless you uninstall it ), one way to hack around it is to delete the stores from 2.0 in the editor ( this will only remove the custom post types, but make a backup anyway ).

    Open phpMyadmin, import the stores the way you used to in the old db table. Open the options table and set the value for the wpsl_version field to 1.8, reload the dashboard and it will ask you to convert the store locations in the old db to the 2.0 custom post types again. It’s not the most user friendly way, but until I release the CSV add-on, I think this is the only way.

    Thread Starter YesThatAllen

    (@ahancock)

    Aha! setting wpsl_version 1.8 was the thing I didn’t know… nice work!

    I had to create the table wp_wpsl_stores and put the items in there, but the conversion was fast and pain-free.

    Thanks so much!

    Plugin Author Tijmen Smit

    (@tijmensmit)

    Good to hear it worked out!

    A more user friendly option will be available soon ??

    it worked in my case.

    I’m having a problem that is related to this situation, but not precisely the same:

    1. There is another store locator type plugin on a site that someone else built. This plugin is not up-to-date, so I’d like to switch it to this plugin.
    2. This plugin was installed, but not activated.
    3. The plugin files were from 9/14, so I updated them first.
    4. I have an export of the locations, but the old plugin was never activated, so there are no tables in the database to import into.
    5. I have the files from the old plugin, but the Dashboard does not recognize that they are there when I replace the new files with the old files.

    Any thoughts?

    Plugin Author Tijmen Smit

    (@tijmensmit)

    @nora McDougall Do you have a CSV export from the other store locator? If so, then you can import them into the db table from 1.2.25 with phpMyAdmin. You do have to make sure the headers in the CSV file match with the ones in the WPSL db.

    After you imported them through phpMyAdmin, install the 2.0 version and the table from 1.2.25 is detected and the upgrade procedure will ask you to convert them to custom post types.

    Hi Tijmen.

    First of all thank you for this cool plugin.

    I have a fresh V2 install without an old table – therefore I don′t know about the structure of the old table and how to export / reimport it.

    EDIT: Whoops, just found the docu-link to the structure, sorry…

    My real question is: will the CSV-option be part of the free plugin or will it be commercial? And do you have an idea when the option will be available?

    Thank you and kind regards.

    Sascha

    Thread Starter YesThatAllen

    (@ahancock)

    Hi Nora,

    This is a sql command which should set up the old table

    https://gist.github.com/YesThatAllen/5d750f7ffeedc07d46fd

    Tijmen – I look forward to seeing your plugin advance, it’s great, and we’ll be first in line to support a Pro version

    Hi everyone.

    OK, I managed to make an import to a fresh 2.0.2 thanks to your documentation and posts – thank you all for that!

    Another question to Tijmen: will the CSV-Import support categories?

    Thanks and kind regards.

    Sascha

    Plugin Author Tijmen Smit

    (@tijmensmit)

    @darthsaschi it will be a paid add-on, and yes, it will support categories. I’m hoping it will be available in the coming weeks

    YesThatAllen,

    Thanks a bunch for the SQL to create the table! You saved me a bunch of time digging it out of my archive backups!

    Now that I have a table structure and data, I have some questions.
    1. Do the IDs start at 0 or 1?
    2. The telephone numbers exported with no punctuation. Will it be added or is there a specific format? It looks like a plain text field, but is there a filter in the code?
    3. States is a straight text field. I’m guessing the mapping is done strictly by lat/long, so the state could be altogether incorrect and the mapping would still function, ie. no error checking.

    Data conversion is always such an adventure!

    Thread Starter YesThatAllen

    (@ahancock)

    Ha ha ha, yes, that’s why I pay good money for nice friendly converters.

    Tijmen.. thanks for your work on this plugin, will be glad to be one of your first paid supporters.

    Tijmen Smit,

    Thanks of a great plugin. I like the idea of a bulk upload but at a decent cost. Others that I saw were like 250 dollars, and as a small company we cannot afford this. I have a fresh version 2 install so the tables that support the old version are not there. When will your update be out?

    thanks!
    Jackie

    Hi all.

    I have a problem with the import as described above. I just tried this for a multisite ID2 – so the import does not work. I can only import to ID1. Is there a way to get the locs to multisite ID>1?

    Thank you all and kind regards.

    Sascha

    Edit: I tried a standard WP export / import and basically it works, but a lot of locs are skipped this way because they share the same name. Any help would be appreciated.

Viewing 15 replies - 1 through 15 (of 36 total)
  • The topic ‘Import into v2?’ is closed to new replies.