June 19, 2015 at 1:20 PM #30796
Please see link below with warning messages:
Anyone know what causes this? Worked fine on my dev site but shows these warnings once moved to the live site. Both were on the same hosting environment.
I have attached a screenshot of the versions I have installed.
Attachments:You must be logged in to view attached files.June 19, 2015 at 1:32 PM #30798
I have updated the Pro Pack. No longer getting the warning messages on the map page (link in previous post) but still getting the warning messages on the admin locations page. Plus the locations do not seem to load on the front-end map page.June 22, 2015 at 5:37 PM #30869
Nick, Thank you for providing the information. Please check for possible issues under:
I have tried the steps in the link with no luck. I am getting errors on the admin loactaions page. I have attached a screenshot. Could this be the issue?
Attachments:You must be logged in to view attached files.June 23, 2015 at 7:24 PM #30917
Export your locations file to CSV , check the formatting is the sl_tags column correct?June 24, 2015 at 12:11 PM #30933
If you upgraded from a pre-4.2 version of WordPress to WP 4.2 and this started happening it is most likely due to the fact the WordPress significantly revised the custom taxonomy system.
The easiest fix, until I write an extensive patch to work through the WordPress 4.2 rewrite, is to unload / delete your custom Tagalong categories then re-create/re-load them. It is best to do this via a location export first, delete the location categories via the category manager in WordPress (via Tagalong tab : Category Manager link), then re-load your exported locations.
This process will recreate new internal category IDs used by WordPress and attach those new IDs to your locations.
I do not recommend trying to manage these manually as there are several linkages involved between location data and the WordPress categories.
The taxonomy patch will get done eventually, but the unfortunate part of this is that the tools available for WordPress 4.2 is only a “best guess” scenario and will require a lot of overhead during the Tagalong update.
You must be logged in to reply to this topic.