Organizer data erased and blank organizer added when error message returned

[Sean]

Unfortunately, this issue was not fixed in 4.0.1. Please advise. Thank you.

[Sean]

As mentioned before, the end user can easily get into an endless loop if they do not enter a required field when submitting their event (simply because most will fix the missing required fields but it will understandably not occur to them that their organizer information was erased and/or that a blank organizer was added, which returns another error when they try to resubmit). So we’re really hoping that a fix can be released shortly, as we are unable to use Community Events in the meantime.

Otherwise than this lingering issue, 4.0.1 seems to have fixed the other key problems with the Submit an Event form, so thank you for that!

[George]

Hey @Karly,

I’m sorry to hear that issues are persisting!

There are three specific things I would recommend doing:

1. Share your “system information” with us – here’s how: https://theeventscalendar.com/knowledgebase/sharing-sys-info/

2. Go to your WP-Engine page in your site’s wp-admin, and make sure that all caching is disabled. Also, clear the caches that are available to clear. (Contact WP Engine for help with doing this if you’re not familiar).

3. In the same WP-Engine page in your site’s wp-admin, click “reset file permissions”. (And again, contact WP Engine for help with doing this if you’re not familiar).

Do these steps make any difference with the behavior on that page?

Thank you for your patience with this issue!
George

[Sean]

This reply is private.

[George]

Hey @karly,

Thanks for this. I’m curious about these two things:

1. Have you done the “Reset file permissions” step I recommended above? If not, try it and see if anything improves.

2. The WP Engine staging site system can have odd behaviors. I looked up this bug in our development system and can see that our fix for it was, indeed, included in 4.0.1, so I’m just curious about why this is still happening and have had many inconsistent behavior problems that arise from the WP Engine platform specifically….

So, can you try resetting the file permissions, then regenerating the staging site from within your WP Engine dashboard?

—

Thank you for your patience with this!

Sincerely,
George

[Sean]

Hi George,

Yes, we have reset file permissions. Also, we have confirmed this bug still exists on a local install (which should eliminate WP Engine being the source of the problem). We are launching at the end of this month, so we are not working on our Production site; only the staging site. That’s why we went ahead and tested on a local install – to ensure it wasn’t a problem within the staging site.

Although the fix was apparently included in 4.0.1, was it actually verified on a live install? If so, wpshindig must not be running the latest version? Because the issue is present there as well 🙂

Looking forward to your response, as this is a potential roadblock to our launch later this month!

Thank you.

[George]

I appreciate you investigating all of this Karly. I’m really sorry about the approaching deadline, we’ll do our best to work through these issues but I cannot promise a conclusion by then, of course 🙁

The good part, I guess, is that this would only be an issue for folks who don’t succeed in filling out the form. I am NOT dismissing the problem! Just trying to find the utility that exists outside of this problem – I hope that it is not a full-on, show-stopper problem because of a minority of users who might not fill out the form correctly. In either case, we are working on a series of bug fixes – this one was supposed to be fixed, but I have reached out to developers and will be diving into the code myself today to try and make progress on this.

Thank you for your patience with us. I am genuinely, seriously sorry about all the trouble resulting from this bug.

Please stay tuned to this thread, I will be posting updates as soon as possible.

Sincerely,
George

[Sean]

This reply is private.

[George]

Thank you so much for sharing this!

I will still be investigating your issue, and will include this fix if possible. At this time, the best news I have is unfortunately “stay tuned for our upcoming releases”, because we will be rolling out releases in the new year to fix a number of problems like this one and others…

I’m sorry about the lack of specific and immediate action that can be taken here! However, I hope that your partial fix keeps things somewhat working for now.

I will close this thread for now but please stay tuned to plugin updates – look for the second update to come in 2016! If this update does not fix things, open a new thread and we’ll take another look into this.

I’m sorry for all of the trouble Karly!

Best of luck with your site in the meantime.

Sincerely,
George

[Leah]

Hello,

Thank you for reporting this issue. We weren’t able to get a fix for it into our upcoming release (4.1). However, please know that the problem is still on our radar and is ticketed within our system to be addressed in a future maintenance release. We’ll do our best to keep you posted when we are able to get a solution in place. Thank you for your patience while we improve and expand our plugins.

Best,
Leah

[Brook]

I just wanted to thank you once again for reaching out to us about this. We just released a new version of The Events Calendar and all of its addons that contains a fix for this.

Our blog post with the full details: The Events Calendar 4.1.4 and premium add-ons

We recommend updating as soon as you can to get the latest patches. Please let us know if this fixes the bug you have been experiencing or if you have any follow up questions. Thank you again!

– Brook

[George]

Indeed! The new version is out; let us know if it helps!
George

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts