So Themes Conflict with The Events Calendar

Hi Pete

Thanks for the update.

The forum doesn’t support attachments. Screenshots can be shared by uploading to any accessible location online and posting the link.

Please confirm that a test has been done with only Events Calendar, Events Calendar Pro (just two plugins activated, nothing else) and Corp.

Are the events created in the Classic or Block Editor?

Thanks for the detailed updates.

Both GeneratePress and Hello Elementor exhibit the same behavior. Perhaps you can confirm that finding? Please try testing with any notable third-party theme that’s not core WP and not SiteOrigin. If you can confirm my finding then it places the responsibility on The Events Calendar to resolve.

Claude’s Code’s findings below.

SiteOrigin Corp Theme Difference:
– Feature-rich functionality: Corp theme includes advanced features like sticky headers, smooth scrolling, mobile menus, fullscreen search, and portfolio filtering.
– Multiple library integration: The theme integrates several specialized libraries (Isotope for portfolio layouts, FlexSlider for sliders, FitVids
for responsive videos) to provide enhanced user experience.
– Script execution timing: This comprehensive functionality creates a different script execution environment that affects when other scripts can access global objects.

Twenty Twenty Four Works Because:
– Block-focused approach: Only uses init action for basic block styles and CSS enqueuing.
– Minimal script footprint: Doesn’t register custom JavaScript, relying on WordPress core and block editor functionality.
– Simplified execution context: No additional libraries or complex interactions that could affect plugin script timing.

The Technical Issue:
SiteOrigin’s comprehensive feature set creates a different JavaScript execution environment where:
1. WordPress loads scripts in the correct dependency order.
2. The theme’s feature-rich scripts initialize their functionality.
3. The Events Calendar’s category-color-selector.js tries to access tribe object.
4. The timing of when the tribe object becomes available differs from simpler themes.

Executive Summary: SiteOrigin Theme Compatibility Issue

Problem:
The Events Calendar’s category-color-selector.js fails on SiteOrigin themes with “tribe is not defined” error, breaking category color functionality.

Root Cause:
TEC assumes the tribe JavaScript object is immediately available when scripts execute. SiteOrigin themes create a different
script execution environment where this assumption fails.

Technical Fix Required:
Add defensive JavaScript checks in TEC’s category color selector script to handle cases where the tribe object isn’t immediately available.

Implementation:
Modify the category color selector to either:
– Check for tribe existence before using it
– Implement a retry mechanism if tribe isn’t ready
– Use proper dependency management to ensure load order

Solution Ownership:
TEC needs to make their JavaScript more defensive to handle different theme execution environments, rather than assuming immediate object availability.

Sounds like a plan! Please let us know how you get on.

Cheers

Andrew