conflict with The Events Calendar

Hi @alwiggins,

I installed The Events Calendar plugin and added an event to test out the flow. I was not able to replicate the error on my end, unfortunately, so I am not sure how to replicate this behavior. I honestly am not sure what would be causing that error and the error is not very explicit. I find it strange that this error is pointing out core files from WordPress as well. Do you happen to have any other errors? Perhaps if you enable debug logging, you might catch or see additional errors?

Here are instructions for debug logging.
https://www.ads-software.com/documentation/article/debugging-in-wordpress/#wp_debug_log

Here is a test event that I put up.
https://njc.f0f.myftpupload.com/?post_type=tribe_events

Best regards.

I had a thought about the nature of the error regarding passing by reference. It could potentially be related to PHP versions. Can you identify what version of PHP, WordPress, and CoBlocks you are running?

WordPress 6.4.1
PHP 8.1.13
CoBlocks 3.1.5
The Events Calendar Pro 6.2.4

Thanks for your comments. I am attempting to create a local host multisite that I can test on . Hopefully something will be revealed

I have recreated part of my multisite network on a local host. This network contains just the primary site and one of the subsites that is experiencing the conflict between CoBlocks and The Events Calendar. I installed the same theme and plugins as the live network. On the subdomain site I only activated three plugins: Blocksy Companion (Premium) required by theme, CoBlocks and The Events Calendar. The error persists will only these 3 plugins. I only activated the basic Events Calendar, not the Pro version. Warning: CoBlocks::{closure}(): Argument #1 ($post) must be passed by reference, value given in?C:\Users\Craig\Local Sites\mgfws-multi\app\public\wp-includes\class-wp-hook.php?on line?326

When I activate The Events Calendar Pro the error remains. I am at a loss because there is nothing else to deactivate and if I lose either CoBlocks or The Events Calendar I will break at least 10 sites.

Do you have any other ideas?

I decided to go to different local site that I have that is not multisite. It has Blocky and CoBlocks installed but not The Events Calendar. I installed the free version of The Events Calendar and created an event. when viewing the event, the error appeared on this event page just as on the multisite network. To test the theme, I changed it from Blocksy to Twenty Twenty-Two and the error continues to appear. This local site is also on a slightly older WordPress version 6.2.2 instead of 6.4.1 So I have narrowed the problem down a bit. It’s not the recent WordPress update nor the multisite network and it is not the theme. The only common denominators are CoBlocks and The Events Calendar.

Update – through an iterative process of rolling back plugins and switching themes I have eliminated the error message by rolling back CoBlocks to version 2.25.5. With CoBlocks set to 2.25.5 it does not matter what theme or version the other plugins are on, there is no longer an error message.

In our multisite network, we do not allow autmatic updates to occur because of the difficulty diagnosing problems like this once they occur. In this case I allowed several plugins to update through multiple versions and did not catch the error right away thus complicating the task of troubleshooting. I now have a solid method to test updates in a local test environment prior to updating on the live network.

Thank you for your input. I hope you will be able to determine what in Coblocks is causing the conflict so we can continue updating. For the time being, we will hold steady on version 2.25.5

• This reply was modified 1 year ago by alwiggins.
• This reply was modified 1 year ago by alwiggins.

Update: Further investigation and finally discussion with The Events Calendar has revealed the REAL problem is that The Events Calendar is not compatible with PHP versions 8.x

I apologize for my last comments that it was pointing to CoBlocks. While rolling back CoBlocks did result in the removal of the warning error, I was able to update Coblocks to current version after rolling back PHP to ver 7.4.

thank you again for your earlier comments and patience with me while I eliminated CoBlocks as a source of my problem.