[etcwebdiv]

Jaime,

Thank you for the reply. For now I am just going to use the first filter you referenced, to make the Event Description not required. I would prefer to keep that field required, but if the datepickers are not going to retain their data if a required field is left empty, that’s a choice I have to make.

Upon further review, I found that this is a known bug:
https://theeventscalendar.com/support/forums/topic/submission-form-required-fields-and-error-message/#post-1396257

Is there any ETA for resolving this issue? Once it’s resolved I can then remove this filter, to make the Event Description/post_content required again.

Thank you for your time.

[etcwebdiv]

This reply is private.

[etcwebdiv]

This reply is private.

[etcwebdiv]

Victor,

Thanks for the reply.

The issue is with “Layouts”.

As I mentioned, I also posted a question on their support forum. They replied first, and I have just made an adjustment to the /tribe-events/default-template.php file in my theme that allows the Community Events “Add” page to display – instead of just a white screen. The first custom default-template allowed the main Events page to display but didn’t work with Add Community Event.

This solution essentially strips out everything generated by the Layouts plugin. It eliminated the conflict, but also left me with unstyled default elements in the header and footer. So I have more work to do, but I am now past this latest hurdle.

Ultimately I would love to see an “integration” plugin or something similar that would get both plugins to work better together. My research of prior support topics from others experiencing similar problems, and creating my own topics, is getting me there – but it’s taking time.

[Author]

Posts