Bad Errors with Organizer updates

[Mad Dog]

We just went live and users are having problems with the Organizer information.

1. If they try to update their Organizer information they’re getting the following ugly PHP error:

Fatal error: Call to undefined method Tribe__Events__Community__Organizer_Submission_Scrubber::filter_organizer_data() in /home/sitename/public_html/THAI/wp-content/plugins/the-events-calendar-community-events/src/Tribe/Organizer_Submission_Scrubber.php on line 30

There’s more, but let’s start there.

Thanks,
Mad Dog

[Cliff]

Hi Mad Dog. I hope to help resolve your issues.

Could you please provide more information so I can investigate further? For example, the link to where the error is happening, any custom code you have implemented, and your system information:

Make sure to use the “Set as private reply” checkbox to protect your private information from the public.

You can find the system info by going to WP Admin > Events > Settings, clicking on the “Help” tab, and scrolling down to the “System Information” box. (Or by going to [yoursite]/wp-admin/edit.php?post_type=tribe_events&page=tribe-events-calendar&tab=help)

That will give me a lot of extra information to help diagnose the problem.

[Mad Dog]

This reply is private.

[Cliff]

Mad Dog, thanks for all the details.

I’ve had our developers look into this and it’s now a confirmed bug. Thanks for your help reporting it.

It’s definitely a high priority one and I’d hope it gets included in an upcoming release, but I can’t give any ETA. This ticket should get updated once the fix is released though.

Thanks!

[Mad Dog]

I guess I’m glad it’s not in the site set-up but this is a pretty bad one. None of our users can update their organizer information.

– I’m curious what is causing this bug to occur since apparently other people aren’t having this problem or you’d be swamped with complaints.

– Is there anything I can do temporarily so our users can update their organizer information? I have no problem making a change to a core file if need be, knowing the true fix will be in an update. This is an important feature to have working.

Thanks for looking into this and getting the developers on it.

Mad Dog

• This reply was modified 10 years, 5 months ago by Mad Dog.

[Cliff]

I double-checked with the devs and the answer is, unfortunately, to just wait. It is high priority so should come soon. If you want to dabble, you may be able to comment out the line that’s throwing the error but that’s untested and at your own risk.

We’re on it and should get you the fix soon!

[Mad Dog]

Thanks. I’ll leave it alone for now. Hopefully not many people will try to change their info and if they do I’ll take care of it manually for them.

Keep me posted on progress or if there’s anything I can do to help test their solution.

MD

[George]

Just commenting on this thread to let you know, Mad Dog, that we’re still working on this but are approaching a release. We’re hoping to get something out the door before the end of the month at the latest, if all goes to plan. 😀

Stay tuned!
George

[Author]

Posts