[Rob]

Hey mindfeck! Thanks for the follow-up here, and I’m sorry we failed to see your last comment. I’ve made sure Barry is aware of it so he can reply in as timely a fashion as possible. Thanks for your patience on it so far.

[Rob]

Hello there Luke! Thanks for this note, and for your words on the plugin. Awesome to hear you’re enjoying it. This was an interesting question and one I actually had to go to the dev team to get a reply on, but I do have some information that should help point you in the right direction.

Admittedly, it might not be worth the trouble to actually use a different post type for organizers (especially since from the sounds of things you’d need to do it in all 3 plugins). But you could definitely either add a custom taxonomy called COMPANIES, and use it with our Organizers. But another dev also suggested either:

* using a save_post callback to update all three in some arbitrary way whenever one is updated; or
* using a filter so select data is always pulled from the same place

I hope that helps. Realize it may not be entirely along the lines of what you’re looking for, but it’s admittedly probably the best we can offer up at this point. Please let me know if you have other questions or need anything else here.

[Rob]

Fantastic to hear this got you sorted, thindes57! We really appreciate you using the plugin, and your ongoing support. If we can do anything else please just let us know.

[Rob]

Glad to hear you got it sorted in the end! I’m not sure I understand your new goal, though: are you saying you’d like to set the number of events that show per page? Or something else? Please let me know and I’ll do my best to get you sorted on this end.

[Rob]

Hey Alex. Thanks for the note here, and sorry to hear of the inconvenience you’ve experienced here. As you may be aware based on our past exchanges, we’re committed to getting everyone’s issues sorted here to the extent we can.

While admittedly the deactivation route is pretty common practice for identifying conflicts with WP plugins or themes, I can see how you’d be frustrated at the request to do this. Unfortunately there are situations where we really have no other option at identifying the source of an issue – such as here, where this is certainly not the default behavior of the plugin and does sound like something specific to your install. Thank you for taking the time in your subsequent message to give it a go and see what might have been the issue.

I’m finding that all 3 of the links you’ve provided here – the original main site link, the events page and the specific event you linked to – aren’t working for me. Have you already deactivated the plugin and moved onto another solution? If not, can you provide me a functional link so I can do my best to get you sorted here?

Thanks for your patience so far.

[Rob]

Hey there Steve. Glad to hear you ended up finding a solution that didn’t conflict here 🙂

I’m afraid my news on the WPML front won’t do much to ease your mind: WPML at the moment is unfortunately one of the main plugins we know ours does not adequately integrate with. We do have plans to focus on fixing that integration this year, and the WPML team have made themselves available for that when we have resources, but we’ve been so focused on getting 3.0 out and now stabilized that we haven’t had a chance to focus there yet.

Know that it’s on the radar, though – we get a ton of requests for this and we realize we’re not staying as competitive as we could by failing to integrate properly. I suspect accomplishing this will be done sooner rather than later, as a result. Sorry I couldn’t offer you more…but please let me know if you have other questions.

[Rob]

Hey hubsaltlake! We totally can still help you out here. Barry’s operating at half capacity this week, so he may be done for today already, but I’ve passed this his way so we can prioritize a follow-up tomorrow at the latest. Thanks for your patience on this end so far.

[Rob]

Thank you, Tara! No worries at all about the delay. Just a heads up that I’ve got this back on the radar and will have Jessica take a look shortly, to finish what we started in my August 5 note. Stay tuned and thanks for your patience so far!

[Rob]

Just wanted to make sure you saw snorton’s follow-up here, akbradley57. Let us know what else you need here.

[Rob]

Thanks Andy!

[Rob]

Hi frantgotier. Thanks for the note here. You’ve indeed stumbled into a couple of bugs here that we’ve got logged in our system and are working to address for the impending maintenance release: namely, that the featured venue widget isn’t showing events when it should. This is a high priority for us and we’re working hard to patch it as quickly as possible.

As for the list widget: that’s a problem I actually haven’t seen reported yet, and looks – unlike the first item you reported – to not be in our system yet. But I was just able to recreate it locally so it looks like this is indeed a legit bug in the current codebase. I’m going to do my best to get this one included in the forthcoming maintenance build as well, now that it’s on the radar.

Thanks for your patience and apologies for the inconvenience as we work to get this sorted. Please let us know if we can do anything else.

[Rob]

Hey Robin! Thanks for this. This one is a real doozy; I just spent a few minutes trying a wide range of recurrence patterns/edits, all of which ended with me following your steps – breaking one out with a different description, to mimic the dinner scenario you’ve faced…and never was the experience anything other than what’s intended.

I talked over the specifics of that error message with the developers, and usually that happens when something gets stuck in a recursion loop; e.g., hook something into save_post, and save a post in the callback, which in turn calls save_post, etc.

We can test if this is an infinite loop issue, though. Just increase the value of xdebug.max_nesting_level in your php.ini, and set it to something like 200. It should solve it; and if it doesn’t, we’ll know this is indeed an infinite loop problem and can try to advise from there.

Thanks for your patience so far. I’ll watch for your reply and will try to troubleshoot as needed then.

[Rob]

Ah, we totally dropped the ball on getting you a reply here tmbond. I apologize for that. While this is a bit outside my personal area of expertise, know that I’ve prioritized it with another member of the team and that we should have you a substantive response in as timely a fashion as possible.

Really appreciate your patience and support in the interim.

[Rob]

Thanks for confirming!

[Rob]

Hey Notionist. Thanks for the follow-up here; bummer to hear the update didn’t fix the problem as it did for Gregg there.

The only real difference between your environments that I’m seeing is Gregg was using the default ordering, whereas you’re running with a tweaked query. My guess is that’s why it’s occurring and why it persists even on a stock install.

Events should order by start date on default…is there a reason you had to tweak the query to begin with? Was that not behaving like it should?

[Author]

Posts