• MonkimoE

    (@monkimoe)


    I’m trying upgrade to geomywp v3.0.1
    Even I’m uninstall/re-install everything and delete all old database previous plugin, it keep telling me
    GEO my WP needs to import existing locations into its new database table.

    Is the notification a bug?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Eyal Fitoussi

    (@ninjew)

    Hi,

    Well, not one has reported this issue yet, but this could be a bug.

    When you first updated to v3.0, did you use the importer and all locations were imported properly?

    pmcreations

    (@pmcreations)

    SAME ISSUE. I lost all 100 of my BuddyPress user locations. I need to repost each one individually. In buddypress location tab it now says “The member has not added a location yet.”

    Seriously guys!?!

    Plugin Author Eyal Fitoussi

    (@ninjew)

    Hello @pmcreations,

    After updating to GEO my WP 3.0, did you use the v3.0 importer to import existing users to the new database table? You can find the importer in GEO my WP -> Import /Export -> GEO my WP v3 importer.

    The old database table is still there, GEO my WP does not remove the table after the update to v3.0. So the locations of your members should still be in the database. It is just a matter of importing them to the new database table.

    Thread Starter MonkimoE

    (@monkimoe)

    Importer to Geo my WP 3.0 success. but still showing me the notification.
    Even I already delete my table from my database as the function detects:
    wppl_friends_locator
    {$wpdb->prefix}places_locator

    So I need to disable it manually T_T
    commented at class_gmw_admin.php line 25:
    //add_action( 'admin_notices', array( $this, 'update_database_notice' ) );

    Now the Member Locator tab in Import/Export show blank because tables doesn’t exist.

    pmcreations

    (@pmcreations)

    Eyal,
    YES – It worked for me.
    Thank You Very Much for answering my issue!
    Sincerely,
    pmcreations

    Location import wouldn’t work for me and the message wouldn’t go away. After manually re-adding my custom post type locations, these database steps stopped the notification from appearing:

    1. Delete old table wp_places_locator
    2. Delete gmw_old_locations_tables_exist in wp_options

    Use at own risk. To check it won’t break anything you could rename the table before deleting.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Needs to import exsiting locations into its new database table?’ is closed to new replies.