Dear Support,
We love this theme however we run into a conflict and need your help. We’re using the Events Calendar plugin and for whatever reason, (it’s not the booster plugin because that was disabled) we’re getting the following error:
wp booster error:
td_module: td_module_15($post): $post is not WP_Post
/home/website/public_html/wp-content/themes/newspaper/includes/wp_booster/td_module.php
It seems to not be detecting what the Events Plugin is parsing on this page. We need to make this error disappear. Please help.
Thank you.
Hi,
This error is not related to speed booster plugin.
Please provide more details how/what did you added in the page and also if you made any custom modifications to the code. Paste also a link to this plugin that you use if is free.
Thanks!
There’s nothing added to the page. It’s a system page put out by the Events Calendar plugin, so basically that page doesn’t physically exist, it’s just dynamic from the plugin. There’s been no custom modifications made to any code within the theme or plugins related to it. It’s just throwing this error out of the gate when I installed the theme.
Here’s the link to the free Events Calendar plugin: https://wordpress.org/plugins/the-events-calendar/
Thank you for your help in helping resolve this conflict.
Hi lwweb,
I also have the “The Events Calendar” plugin active on my side but I could not recreate your issue, the event appears on category page as it should.
Please check this without any plugins active except of Visual Composer and Events plugins, clear cache and see if you still have this issue. Also if you use child theme, switch to the main theme and verify this.
If the issue persist please send an email at contact@tagdiv.com so we can take a look(provide more details, the page where you have this issue..), also paste a link to this topic so we can know who you are and what your issue is.
Thanks!
Hi Alin,
I figured out what the issue was. In the plugin’s calendar settings under the display tab, the default template was set to “Default Events Template”, so I switched it to “Default Page Template” (theme’s default page) and the error went away! So I think that was the issue. Everything looks good now.
Thank you for your very prompt replies in regards to support. That’s impressive!
