|
endora
|
May 4, 2016 at 12:21 pm
In addition to EE categories we also have a regular WordPress blog on the site. When going to a WordPress category page it’s trying to load EE code. When I compared a page that worked to one that didn’t here is the extra code that was in the page that didn’t work (I had the same issue on a regular page–not a category page). The single post page is working fine.
<link rel=’stylesheet’ id=’ticket_selector-css’ href=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/assets/ticket_selector.css?ver=4.5.1′ type=’text/css’ media=’all’ />
<link rel=’stylesheet’ id=’single_page_checkout-css’ href=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/css/single_page_checkout.css?ver=4.8.36.p’ type=’text/css’ media=’all’ />
<div id=”espresso-notices”></div>
<div id=”espresso-ajax-loading” style=”display:none;”>
<span class=”ee-spinner ee-spin”></span><span style=”display:none;”>loading…</span>
</div>
<div id=”espresso-ajax-notices”>
<div id=”espresso-ajax-notices-success” class=”espresso-ajax-notices success fade-away” style=”display:none;”>
×
<p class=”espresso-notices-msg”></p>
</div>
<div id=”espresso-ajax-notices-attention” class=”espresso-ajax-notices attention fade-away” style=”display:none;”>
×
<p class=”espresso-notices-msg”></p>
</div>
<div id=”espresso-ajax-notices-error” class=”espresso-ajax-notices error fade-away” style=”display:none;”>
×
<p class=”espresso-notices-msg”></p>
</div>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-includes/js/underscore.min.js?ver=1.8.3′></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/core/templates/global_assets/scripts/jquery.validate.min.js?ver=1.15.0′></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-includes/js/jquery/ui/datepicker.min.js?ver=1.11.4′></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/core/templates/global_assets/scripts/jquery.validate.additional-methods.min.js?ver=1.15.0′></script>
<script type=’text/javascript’>
/* <![CDATA[ */
var ee_form_section_validation_init = {“init”:””};
var ee_form_section_vars = {“form_data”:{“ee-single-page-checkout-dv”:{“form_section_id”:”#ee-single-page-checkout-dv”,”validation_rules”:[],”errors”:[]}},”localized_error_messages”:{“validUrl”:”This is not a valid absolute URL. Eg, http:\/\/domain.com\/monkey.jpg”,”regex”:”Please check your input”}};
/* ]]> */
</script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/core/templates/global_assets/scripts/form_section_validation.js?ver=4.8.36.p’></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/jquery.plugin.min.js?ver=1.0.1′></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/jquery.countdown.min.js?ver=2.0.2′></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/js/single_page_checkout.js?ver=4.8.36.p’></script>
<script type=’text/javascript’ src=’http://www.atthemac.org/wp-content/plugins/event-espresso-core-reg/modules/add_new_state/assets/add_new_state.js?ver=4.8.36.p’></script>
|
|
endora
|
May 4, 2016 at 12:30 pm
The body tag is as follows:
<body class=”archive category category-blog category-60 logged-in admin-bar no-customize-support custom-background”>
|
|
Josh
|
May 4, 2016 at 12:52 pm
It turns out that a regular WordPress category archive page will load up Event Espresso code because because if one of the posts in that archive has an Event Espresso short code in its content, the code needs to run.
That said, none of the code above should cause anything to break though. Can you explain what’s not working with your category archive page, and maybe post a link here so we can investigate?
|
|
endora
|
May 4, 2016 at 12:55 pm
Thank you. It is breaking the calendar in the sidebar. http://www.atthemac.org/category/blog/
|
|
Josh
|
May 4, 2016 at 2:00 pm
Hi there,
I’m not certain if this will fix the calendar, but you can try adding this code to your theme’s category.php template:
<?php add_filter( 'FHEE__EE_Front_Controller__display_errors', '__return_false' ); ?>
You add it just before where it has this:
<?php while ( have_posts() ) : the_post(); ?>
If that doesn’t help please let us know and it may help to be able to look at the calendar widget plugin’s code.
|
|
endora
|
May 4, 2016 at 2:31 pm
I am sorry to say that that did not change anything. The calendar that is being used in the sidebar is not the EE Calendar Widget it is the Blog Post Calendar.
|
|
Josh
|
May 4, 2016 at 2:38 pm
Where would I be able to download the plugin that adds the blog post calendar?
|
|
endora
|
May 4, 2016 at 2:39 pm
https://wordpress.org/plugins/blog-post-calendar-widget/
|
|
endora
|
May 4, 2016 at 4:08 pm
I am sorry, but I need to remove the calendar from the sidebar while it’s still broken; however, I think you should still be able to see that extra code that’s added to the category pages. The main news page has the calendar rendering fine and doesn’t have the extra code. Thank you.
|
|
Josh
|
May 4, 2016 at 5:47 pm
Hi there,
I’ll see what I can do about putting together a code snippet that will dequeue the extra CSS and JS from loading on that category archive page as a stop gap fix for this.
|
