Anonymous Users Can't Add New Venues or Organizers

[Sean]

Hi guys,

It appears that this issue was resolved in 3.12.6, but we are running 4.0rc1 and the issue seems to persist: If a user is not logged in, it is not possible for them to add a new venue or organizer. When a user is logged in, the issues is resolved.

In our case, we must allow users to submit events without being logged in. Can you please confirm if the patch to fix this issue was included in Release Candidate 1? If not, will it be included in the official release of 4.0 later today?

Thank you.

• This topic was modified 10 years, 4 months ago by Sean. Reason: Added link to original topic/issue
• This topic was modified 10 years, 4 months ago by Geoff.

[Sean]

Updated to the official 4.0 release and found that this issues persists on a clean local install as well (WordPress 4.3.1, Twenty Fifteen Theme, and only TEC, PRO, Community Events and Filter Bar plugins installed).

When an anonymous user submits an event, they cannnot create a new Venue or Organizer. The user can select an existing Venue from the dropdown, but it defaults to selecting the existing Venue (thus no way for the user to add a new Venue).

For the Organizer, the meta fields are not displayed, including the Use Saved Organizer dropdown. The only content that is displayed in the Organizer module is “add another organizer. Upon clicking that option, the user can enter data in the fields. However, the content is not saved when the form is submitted.

[Sean]

This reply is private.

[Geoff]

Hi Karly, thanks for getting in touch!

I’m so sorry for the trouble here. This is indeed a bug that we have logged a ticket for in our system. Unfortunately, I do not have a timeframe for when it will be patched, but I have added this thread to the ticket and will be sure to follow up with you when I know more. I’ll set this thread to Pending Fix in the meantime.

Thank you for your patience while we figure this out!

Geoff

[Sean]

Thanks Geoff. Since the issue was fixed in 3.12.6, it probably is just a matter of merging the code. But if a fix won’t be released in the coming days, can you please ask what code was changed in 3.12.6 (which had originally fixed this issue) so that we can manually resolve the problem on our install prior until the patch released? Thank you!

[Frank]

Hi all,

I have the same issue. Just writing here to be notified via email.

Kind regards,
Frank

[Geoff]

Hey there,

I dug into this deeper with one of our lead developers. The crummy thing is that you are indeed right, Karly: this was fixed in 3.12.6 and leaked its way back into 4.0.

The good news is that we have already started working on a patch and plan to include it in the first maintenance release for 4.0. I don’t have an exact date for when that’s coming, but we’ve been anticipating it since before 4.0 came out and I would expect it to come soon. Of course, I will follow-up directly here in the thread when it’s coming.

In the meantime, our developer is checking for a possible workaround and i’ll be sure to share that sooner than the release if one is available.

So sorry and thanks again for your patience while we work this out!

Geoff

[Sean]

Thanks for the update Geoff. Glad to hear that the fix previously existed (as opposed to it needing to be patched from scratch!). We’ll be looking forward to the maintenance release, but if your developer is able to come up with a workaround/snippet before then, that would be extremely helpful as we are unable to finish the QA for our project while the bug exists. Thanks again!

[Geoff]

Sure thing! I haven’t heard anything yet but will follow up and let you know if there is more to share. 🙂

Geoff

[Geoff]

Hey Karly,

Will you please installing this plugin (zip)? Our developer whipped it up as a possible patch and I’m hoping it will do the trick. Let me know if it does!

Geoff

[Sean]

Thank you very much Geoff! This seems to have fixed the issue based on our initial testing. We appreciate the prompt attention to this. Another example of awesome support from the Tribe!

Best,
Karly

[Geoff]

Heck yeah! I know we have a few others with the same sort of issue, so it’s awesome to hear it works so we can share it with them as well.

Thanks aa ton for bearing with us and I really appreciate the kind words–your support means a ton to us as well. 🙂

Cheers!
Geoff

[Geoff]

Hey folks,

Just jumping in to let you now that the patch for this issue is included in 4.0.1 and it just released today. Keep your eyes open for the update and please do let us know if any other issues pop up and we’d be happy to help. 🙂

Cheers!
Geoff

[Author]

Posts