|
rayrolando
|
February 2, 2021 at 9:35 am
Event Espresso breaks our category pages. I have deactivated it on our live site…this is what our category pages should look like:
https://rayrolando.com/category/inspirational-one-liners/
When activated this is what it looks like on our dev site:
https://devv.rayrolando.com/category/inspirational-one-liners/
Please advise. At the moment we can not use EE.
|
|
Tony
|
February 2, 2021 at 9:46 am
Hi there,
Looks like this is an issue with the placeholders EE uses to hold notices/errors on the page.
First, you can confirm this by adding this to the dev site:
add_filter('FHEE__EE_Front_Controller__display_errors', '__return_false');
Within functions.php should be fine is using a child theme, although we recommend using a custom functions plugin:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
Does the category page then work as expected?
|
|
rayrolando
|
February 2, 2021 at 10:08 am
Yes that has fixed the issue. So what does that mean moving forward? Will this patch remain necessary or will you include it in an update?
Look forward to your response and thank you.
|
|
Tony
|
February 3, 2021 at 3:08 am
This isn’t something we can fix within Event Espresso other than removing those placeholders. The problem is due to how X-Theme is selecting the article elements on the page which is then thrown off when additional elements have been added.
What you can do is use a snippet like this:
https://gist.github.com/Pebblo/4c374a93c255b57fe262
To selectively disable those additional elements on specific pages.
You can change Line 10 to something like:
if( is_category() ) {
To check for a category list as above, or cover both categories and custom taxonomies using something like:
if( is_category() || is_tax() ) {
If you leave the current code from above in place Event Espresso can not add any notices thrown during registrations into the page so I don’t recommend using the first snippet long term.
|
