table does not exist

Pro Pack will not have any impact on this issue. Sounds like you have had a database path or security change. The kindeye_wrdp2. prefix is not typical for a standard “flat” install of WordPress.

Have you tried using phpMyAdmin or similar tools to see what databases and tables are on your system?

With a clean install or upon re-activating the plugin it will use the built-in WordPress database tool to check for the store_locator data table and for any differences in the table structure. If the table is missing or does not have the most recent structure it will be added/modified accordingly.

If this is not happening either your data settings are not setup properly or you have a security issue that is preventing you from accessing, creating, and/or updating the table.

Any recent changes to the operating system, your web service (Apache?), PHP drivers, or MySQL server can be the culprit. ESPECIALLY if you’ve run any security patches. Even more so if you are on an SELINUX secured system.

Hi there,

Thanks so much for the thorough response. At this point, after several attempts working with my hosting company, it seems there isn’t anything they can do on their end and there haven’t been any changes with the web service.

At this point, all I want to do is re-install the plugin without having it look for the table, because that table definitely is definitely missing. Can you be more specific on what you mean by ‘data settings are not setup properly’? At this point, it seems it’s the only thing I’m left with of the above culprits.

Thanks again,
Rachel

The plugin calls the dbupdate function, which is a built-in WordPress function. It uses the “create database” SQL command and determines if either the data table is missing or outdated.

If the table is missing (in our case this is normally “wp_store_locator” for a normal wp_ prefix on tables) then WordPress will run the proper MySQL commands to create the table.

If the table needs to be updated, meaning we’ve added a column or changed something on the column structure, then WordPress will alter the existing wp_store_locator table.

All of this is done outside of our plugin. We only setup the command to say “we need a table called store_locator that looks like this” and then ask WordPress to manage it for us.

During the activation or installation of our plugin it will run the WordPress function and make the necessary adjustments. What actually happens “behind the scenes” depends on what type of WordPress install you have (WPMU, normal WordPress, etc.), what your table prefixes are set to based on your initial setup, version of MySQL, and security settings. All of that is 100% managed by the WordPress data interface functions.

Hope that makes sense. Bottom line we simply give the table name and structure to WordPress and it takes care of the rest.

– L

Thanks so much for the thorough response! All set, with some help from my database friend. Having that export tool would be super handy should something like this ever happen again, so I’d love to vote for that feature (if you’re keeping track :)). Hope you had a great Thanksgiving! If you’re interested, you can see the store locator in action at https://www.kind-eye.com/go-local/. ??

@remtheory – glad it worked out.

LOVE the icons.

I really need to dig up that cluster marker code from CSL and get that implemented. This is the second time this week I’ve seen a map with way too many markers that close together.

Yes, I’d love the export tool as well. Paid customization/support work feeds the family so those requests take precedence over the stuff I want… like export of locations and cluster markers. It would be very useful for my live “experiment” site at verynearhere.com! ??

I totally understand that and thanks for sharing the experiment site! Thanks again for the super speedy response and hope you have a great week! ??

Rachel