- This topic has 18 replies, 4 voices, and was last updated 9 years, 10 months ago by
.
-
Posts
-
Howdy Jared,
I would love to help you with this.
Would you mind grabbing your system information and pasting it here? Make sure to use the ‘Set as private reply’ checkbox to protect your private information from the public. You can find the system info by going to WP Admin > Events > Settings, clicking on the “Help” tab, and scrolling down to the ‘System Information’ box. (Or by going to [yoursite]/wp-admin/edit.php?post_type=tribe_events&page=tribe-events-calendar&tab=help) That will give me a lot of extra information to help diagnose the problem.
To be upfront this seems like it is probably a theme conflict, maybe a plugin one. Basically the theme or plugin is designed fro an older version of The Events Calendar and they will need to release an updated version for it to be compatible with the latest versions of our plugins. You could isolate which things are conflicting by doing a conflict test. This guide walks you through how to test for a conflict, and then identify what is conflicting.
Cheers!
– Brook
Brook,
I agree that I have a theme/plug conflict that is creating these issues. Yesterday, I upgraded to the new version The Event Calendar Pro, The Event Calendar and your Facebook plugin. I tried to update my theme as it does accommodate your new version(s), however, upon launching the upgrade a fatal error populated stating I had a space issue. I noticed I was maxed out on my memory and disc space so I’m in the process of migrating the site to another, larger server. If I still have these issues after my migration, I’ll reissue a support question in the forum.
That sounds like a good plan Jared. Our threads automatically stay open for 2 weeks from the last response, so feel free to take your time! And if I can help along the way let me know.
Cheers!
– Brook
I still show these errors and it’s very unpleasant. Shall I disable the debug mode in my php file? I’d rather fix what’s broken, however, this needs to be fixed.
You could definitely disable debug mode if needed. But, I might can help you further if you can answer this question:
Were you able finish the conflict test once you got the plugins all updated? Did those errors go away? If so, what is conflicting? I might have an idea on how to fix it.
If I know what is conflicting we can investigate seeing if there is a solution for it. But without knowing what is conflicting disabling debug is probably the only option for now. It is up to you. 🙂
Cheers!
– Brook
Brook,
I did run the conflict test and was unable to see what the issue may be. I’ve reviewed the support tables, I’m not the only user with this issue. All plugins are up-to-date and the error remains. I guess the only thing to do is downgrade your plugin to a previous version because this version is not fit for my production environment? I assume I’d have to downgrade The Event Calendar and The Event Calendar Pro? The error is only associated with The Event Calendar, but I assume the two plugins need to be on the same version.
Thanks for getting back about that.
Indeed we do have a couple of topics about what appears to be this exact issue. It seems to be pretty isolated, in my research I have seen 6 users out of about half a million that reported this. We of course have been doing our best to replicate this issue so we can proceed to find a fix for it, but to date nothing has been found. Hence why I was wondering about the conflict test.
I did run the conflict test and was unable to see what the issue may be.
Do you mind elaborating a bit about this? When you had all plugins disabled and had simultaneously switched themes to Twenty *, did the errors continue showing on certain pages? If so which pages? Some users have indicated it just happens on month view.
I guess the only thing to do is downgrade your plugin to a previous version because this version is not fit for my production environment? I assume I’d have to downgrade The Event Calendar and The Event Calendar Pro? The error is only associated with The Event Calendar, but I assume the two plugins need to be on the same version.
One thing to keep in mind is you should never have WP_DEBUG enabled in a production environment. Not only is it useless in production, it can assist malicious parties in compromising the security of your website. This particular error actually appears to be harmless. So simply disabling WP_DEBUG in production is probably your best option on production as the site will continue functioning fine.
Of course WP_DEBUG is useful on staging servers. And if you are finding that this is a nuisance in staging then yes downgrading is probably the best option. You might be interested in: Downgrading a plugin tutorial. As you suspected, you should downgrade both plugins to matching minor version numbers, I.E. if you downgrade one to 4.1.x it is usually best to downgrade all of them to 4.1.x .
Thanks again for working with me on this. Sorry it has been such a pain.
- Brook
As stated by other users, my errors only show under the month view. If/when I switch to the list view, no errors display. What would the cause of this be?
I have debug mode set to ‘False’ and the errors still display.
I have debug mode set to ‘False’ and the errors still display.
Have you also set WP_DEBUG_DISPLAY to false? That will typically hide warnings.
define('WP_DEBUG_DISPLAY', false);As stated by other users, my errors only show under the month view. If/when I switch to the list view, no errors display. What would the cause of this be?
That’s what we are still trying to figure out. To be up front we might not get to the bottom of it until a user comes along who both has this problem and the time to work with us on troubleshooting it. Until then though hiding the errors should be a good temporary solution.
Were you able to hide the errors following the above?
Cheers!
– Brook
- The topic ‘Same Issues After Upgrade: Warning messages in error Log upon upgrading to versi’ is closed to new replies.