[Damion]

Sorry for the delay. We had to escape the hurricane and won’t be back till Monday.

There wasn’t event data until the import, and there wasn’t a filter bar plugin installed until there were events to filter, so I’m not sure how it would work otherwise, or if it would help to add a few manual ones in to see if it brings the Country filter back to life.

I’m happy to do as you asked as soon as I get in.

Thanks again!

[Damion]

Wow, thanks for taking the time to sort that out.

I got rid of the Country filter and was able to replicate your solution. We do have a few international races, though; will there be a way eventually to have it still work with all filters (including Country) enabled?

These are my error logs for this subsite since it started:

[03-Oct-2016 20:00:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 849
[03-Oct-2016 20:49:56 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 853
[03-Oct-2016 21:01:40 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 849
[03-Oct-2016 21:03:56 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 831
[04-Oct-2016 15:11:17 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 853
[04-Oct-2016 15:16:14 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 853
[04-Oct-2016 15:18:27 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 853
[05-Oct-2016 15:58:26 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/eaglenes/public_html/mrf2/wp-includes/l10n.php on line 849

Which I looked up, which in turn gave me this:

https://github.com/WordPress/WordPress/blob/master/wp-includes/l10n.php which opens by saying

**
 * Retrieves the current locale.
 *

Does that mean WordPress core is giving the plug-in issues? Or could it be a server setup thing, like php.ini needs to be adjusted? I’m not fully versed in networking info, so I wonder if increasing that would make it work, but just to the point of letting people see a crazy long page load? =) I realize we have a lot of events, but I’d hope there was some mechanism we could put in place to keep things as quick as possible given how much info needs to be looked up/parsed.

[Damion]

This reply is private.

[Damion]

Magic!

Venues still had some overwrites, but those remaining appear to be warranted as previously unseen duplicates (in every way, not just the title it was looking for).

Events did overwrites again, even though important information was different between otherwise identical time and identical date events (like location, as well as custom meta we added), it took some and not others. As it was designed to do, but our special case needed leniency.

So I changed the core code, as you said, and far from being fluffy or going madcap, it just generated new events with separate information without trying to qualify it with matches.

Every last one was an insert, and not an update, and the test samples for nearly-identical events (across all meta, keys and values) came through the other side perfectly!

Thanks again for your guidance. It really is a blessing to have this tackled, so that everything else can use the good model of data to its fullest abilities.

Have a great weekend!

[Damion]

Thanks for the update. I just now saw this; didn’t realize notification emails weren’t coming in.

For presentation’s sake, and a few technical and user experience issues, it would be a major issue to have to add to the event names themselves.

We have a lovely bulk delete plugin that lets us do trial and error pretty cleanly with getting these records in, so I think I’ll mix and match. Do the concatenated venues and edit the plugin for event import and see how close we get.

I’ll have to double check the original database records tomorrow at work, then try it, then I’ll come back and let you know how it went. If nothing else it moves the needle way closer to the desired end result.

Thanks so much for checking in again so soon and providing traction on this issue. So far both the free and Pro versions seem to be a crazy good value for how well they deliver, for those people who need what they offer.

[Damion]

Thank you for the clarification on how the duplicate-sniffing mechanism works. The screen is helpful, but it helps sometimes even just to hear it be presented a different way.

Regarding the events, any given kind of race has the exact same title, but all have unique start dates, and being a few hours long, there shouldn’t be any that carry on past that day.

So you might have (this is made up)

“Crazy Fun Raceathon” Tulsa, OK 4/22/2017
“Crazy Fun Raceathon” Culver City, CA 4/29/2017

and since the actual events don’t list addresses, you get just the title and dates, and I’ll have

“Crazy Fune Raceathon” 4/29/2017

or something similar. It treated one example of the series as the only one.

Then, when it went to go find a venue by that same name, and it searched through the venues (that were already condensed by their own anti-duplicate process), it only found that the venue “Crazy Fun Raceathon” is a venue in Tulsa, OK. The other locations were eliminated for being otherwise identical.

so my finished listing looks like

“Crazy Fun Raceathon” Tulsa, OK 4/29/2017

Which is something that doesn’t exist. -A- correct location and -a- correct date, but switched out to not match the date or location to which they belong.

I don’t mind editing the core files, and as a developer I’m very comfortable working with code. Once we’re “patched” we can happily so as I said and do it the “right way” within this new process (which is good and clean and smart and I like it, but it’s different from where we left)….

Ideally, if there could be a way that it would prevent a duplicate if there’s a totally separate address, that would work, but I recognize that, as mentioned before, the system would have a hard time figuring out how to refer to those venues to connect them to the appropriate listing, since without interference they’d find a bunch of matches for the exact same name.

It’s clunky, but I thought about concatenating the venue names. In other words, “Crazy Fun Raceathon” is the event, but there’s two venues, “Crazy Fun Raceathon – Tulsa” and “Crazy Fun Raceathon – Culver City”…then I could programmatically add a body class to events that were before this migration date, and use CSS to hide them so it didn’t look silly and people only saw the address proper.

What was the idea for editing the core for the events duplicates, if you don’t mind me asking?

Thanks again for your help so far, and the quick response time.

[Author]

Posts