Submitted event doesn't "carry over" selected event category

[Rafael]

Hello support

After a community event is submitted it does not “carry over” the event category that has been selected for it. So in the admin backend that event simply has no event category.

This seems to be a new problem. It might have happened after updating all the TEC plugins to the most current version.

Can you help me fix this issue?

[Josh]

Hey Rafael,

Thanks for reaching out to us!

I just did a quick test on this on my local install, however I was unable to replicate the issue you’re describing here. I was able to submit the event and when reviewing on the front-end as well as within the dashboard the event showed the selected category.

As an initial, step can you try going through the Testing for Conflicts procedures to ensure there isn’t a conflict here with an existing plugin or theme?

Thanks!

[Rafael]

Hey Josh

Thanks for your response. I did some more testing and noticed that the problem only occurs for events submitted by non-registered users that attach an image.

Submissions by registered users (both with and without image) or by non-registered users without image don’t have this problem.

Maybe you can replicate the issue with that condition?

(PS: In my testing I’ve always chosen a pre-saved event venue and organizer from the drop-down options. Just in case it makes a difference.)

[Josh]

Hey Rafael,

Thanks for clarifying this one! I tested the steps as well and was able to replicate the issues you’re describing.

I’ve created an internal bug ticket for this issue. You’ll be notified here as we make progress on this one and a fix is readied for release.

Let me know if you have any further questions or concerns about that process.

Thanks!

[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.

[Josh]

Hey Rafael,

Wanted to follow up here to see if the issue persists for your site in version 4.0.5 of the plugin? We were doing some further testing on this one in preparation for hitting it in our next update and notice that this particular issue may have been fixed as a byproduct of another issue.

Thanks!

[Author]

Posts