Duplicate Locations when updating events via WP backend

hi,

this doesn’t happen on my test site; however, we will going to check this out again. also, are you using the latest EM version?

have you tried deactivating other plugins and/or changing your theme to the default WP one to see if this still happens?

how are you deleting the locations?

Hi there, please excuse my intervention in this thread, but I have the same issue found by ontariosea, duplicated null locations, or at least very similar to that.
I don’t know if ontariosea had this too, but when I add an event with the same location of another one, EM searches for existing locations and shows me a dropdown list of matches, even the duplicated NULL ones, but I can’t selct any location because as soon as I move the cursor, or press an arrow key, or even press enter, the dropdown list disappears.
I deleted the duplicated NULL locations directly from the database, because they don’t show up in Dashboard–>Events–>Locations page and can’t be managed from there. They disappeared from the dropdown list, but still I can’t use the dropdown list in order to select an existing location.
My test environment uses WP 3.6, Events Manager 5.5.1, WP FullCalendar 0.8.4, Commons In A Box 1.0.5, S2Member Framework ver. 130816, Portfolio 2.17.

I’ve just set up a new test environment with WP 3.6, Events Manager 5.5.1, WP FullCalendar 0.8.4 and the result is as follow:

• I still get duplicated NULL locations on the database when I add an event, single or recurring and its location. Is it the normal behaviour? The NULL location doesn’t appear in Dashboard–>Events–>Locations but only in the database, and it’s not duplicated when I update the event.
• Locations added directly as a location are not duplicated in the database, not even when I update them.
• now, when adding new events, the dropdown list of suggested location works correctly and allows me to select a previously added location. Maybe in my other environment there is a conflict with the other plugins (unfortunately I need all of them!)

If one of you would like to supply admin and FTP info, I’d be happy to go in and take a look (first come, first served)

Please submit the info on this form and reference this page url so we know it’s you – https://wp-events-plugin.com/contact-us/

Awesome. Sent!

Thanks, will check this out asap and get back to you (likely by tomorrow)

Hi Marcus, I’m using localhost environments and can’t let you take a look, but it seems that on the ‘streamlined’ environment (my second post) I have a NULL location duplicate in the database ONLY when:

• I create a new location while adding an event
• I select for the first time a previously and independently added location from the Location Name dropdown menu, while adding an event. If a location is already ‘attached’ to an event then the NULL duplicate entry is not created in the database.

Maybe this is intentional and the plugin really does the right thing? Adding a ‘standalone’ location, with no event associated to it, doesn’t create the NULL entry in the database.

In my first test, with more plugins activated, whenever I tried to add an event at an already exisisting location, I couldn’t select it from the dropdown menu, and I had to re-add the same location which would result in as many duplications of the same location as the events associated with that location were, and in turn, since I was adding new events, that would create in the database two entries for each repeated location: one with the location data and one NULL.

I’m not able to reproduce this, but hopefully I can do so on ontariosea’s site and finally fix this bug!

I can now confirm that this bug has been identified and fixed locally, the next update (which should be out this week) will contain the fix. Cheers to @ontariosea for letting me test on his site.

Unfortunately this won’t get rid of the previous duplicate locations though. You’ll need to go into the database and delete these yourself.

However, here’s an SQL statement that’ll find all these duplicates for you:

SELECT * FROM wp_em_locations WHERE location_address IS NULL;

this may include draft location posts where you never added an address, but should you delete these rows and re-save that draft, a new row should be created again anyway.

if you’re feeling bold, delete them at once:

DELETE FROM wp_em_locations WHERE location_address IS NULL;

Good news, thanks a lot Markus!

It looks like I have the same problem.

I have loads of duplicate locations in my database and many with NULL values for the address. Every time I go to re-type a location for a new event it gives me a massive drop down of duplicate locations.

Can you tell me how to fix the issue. I can see that the latest version of EM is 5.5.1 so I guess you haven’t released the update that fixes this bug yet?

you can try the latest dev version 5.5.1.1

To upgrade to the dev version see here – https://wp-events-plugin.com/documentation/upgrade-dev-version/