Notice: Trying to get property of non-object in /home/tempsupport0321/public_html/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Permalinks.php on line 30
I have the full expanded notice here:
NOTICE: wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Permalinks.php:30 – Trying to get property of non-object require[‘wp-blog-header.php’], require_once[‘wp-includes/template-loader.php’], include[‘/themes/risen/page.php’], the_content, apply_filters[‘the_content’], WP_Hook->apply_filters, call_user_func_array, Tribe__Events__Templates::load_ecp_into_page_template, tribe_get_view, include[‘/plugins/the-events-calendar/src/views/month.php’], tribe_get_template_part, include[‘/plugins/the-events-calendar/src/views/month/content.php’], tribe_get_template_part, include[‘/plugins/the-events-calendar/src/views/month/loop-grid.php’], tribe_get_template_part, include[‘/plugins/the-events-calendar/src/views/month/single-day.php’], tribe_get_template_part, include[‘/plugins/the-events-calendar/src/views/month/single-event.php’], tribe_events_template_data, tribe_get_event_link, Tribe__Events__Main->getLink, get_permalink, get_post_permalink, apply_filters[‘post_type_link’], WP_Hook->apply_filters, call_user_func_array, Tribe__Events__Pro__Recurrence__Permalinks->filter_recurring_event_permalinks
December 21, 2016 at 9:55 pm
Welcome back 🙂
I notice in your System Information you have the Facebook Events plugin installed on your site. If you’re not aware, we are in the process of retiring the Facebook Events plugin and replacing it with our newest plugin, Event Aggregator.
You have been granted a license for Event Aggregator and it is set to expire on the same date your Facebook Events license expires. For more information, please review our Moving to Event Aggregator Knowledgebase article and if you run into any issues along the way, please create a separate thread.
In response to your original issue: can you please clarify where the error/notice is showing? E.g. your server’s error log or in the backend of your WordPress website when logged in as an administrator.
To continue troubleshooting, you’ll need to review our Testing for conflicts guide and reply back with what you learn. Once we identify the source of conflict, we’ll have a better idea on how to proceed.
Thank you and take care. Cheers!
January 3, 2017 at 10:28 am
I went through the conflict testing, activated the 2016 WP theme, and deactivated all but the events calendar plugins, but I still get the same error:
Notice: Trying to get property of non-object in /home/tempsupport0321/public_html/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Permalinks.php on line 30
January 4, 2017 at 5:13 pm
Welcome back,
Thank you for the response. Are you noticing any effects from the error? Do you notice any reason what action causes the error to display? As previously requested, can you please clarify where the error/notice is showing? E.g. your server’s error log or in the backend of your WordPress website when logged in as an administrator. I’m not able to find any bug reports or threads of users experiencing the same error. I’m also unable to reproduce the behavior on my test installation.
I see you have a plugin to help with debugging. I recommend reviewing Our Favorite Developer Plugins Knowledgebase article for some other helpful plugin ideas.
Please make sure each question gets answered to the best of your knowledge. The more information you can provide, the better idea we’ll have on how to proceed. Thanks again and have a good evening.
January 6, 2017 at 11:26 am
January 7, 2017 at 5:05 pm
Hi and welcome back,
Have you tried flushing your permalinks? Visit Settings > Permalinks in your WordPress admin dashboard and hit the ‘Save Changes‘ button. Check to see if the error goes away. The error displaying at the top of your site is because you have WP_DEBUG set to ‘true‘ on your site’s wp-config.php file. You can set it to ‘false‘ and it should disappear. What is recommended in this situation is set up a clone of your site on a testing environment where you can fully troubleshoot the issue.
We don’t have any logged bugs of users reporting similar issues and I’m not able to reproduce it on my test site. I really wish I could troubleshoot the issue with you in greater detail, but there’s unfortunately not much I can do.
Refer to our Testing for conflicts guide once you have your site cloned to a testing environment and make sure WP_DEBUG is set to ‘true’ until you figure out where the conflict is coming from.
Please keep me updated with what you find out and enjoy the remainder of your weekend. Cheers!
January 18, 2017 at 12:21 pm
Thank you! I edited the wp-config file and that did the trick! 🙂
January 18, 2017 at 6:18 pm
Thank you for letting me know the issue has been resolved and please feel free to create a new thread if you have any more questions or comments. Take care!