{"id":1967125,"date":"2025-10-06T06:35:43","date_gmt":"2025-10-06T10:35:43","guid":{"rendered":"https:\/\/theeventscalendar.com\/knowledgebase\/?p=1967125"},"modified":"2026-04-21T11:42:15","modified_gmt":"2026-04-21T15:42:15","slug":"when-add-on-features-of-tec-dont-work","status":"publish","type":"post","link":"https:\/\/theeventscalendar.com\/knowledgebase\/when-add-on-features-of-tec-dont-work\/","title":{"rendered":"When Add-On Features of The Events Calendar Don\u2019t Work"},"content":{"rendered":"\n

Add-ons for The Events Calendar unlock powerful features, community submissions<\/a>, recurring events<\/a>, filter bar<\/a>, etc. But sometimes those add-ons don\u2019t function properly: they may not show at all, behave unexpectedly, or conflict with other themes\/plugins. Here\u2019s how to understand and resolve those issues.<\/p>\n\n\n\n

Why Add-On Features Break: Root Causes<\/h2>\n\n\n\n

Here are common reasons add-ons stop working correctly:<\/p>\n\n\n\n

    \n
  1. Version Mismatch \/ Plugin Incompatibility<\/strong>
    When you update The Events Calendar but your add-on hasn\u2019t been updated, or vice versa, some functions or hooks may be deprecated or changed. This leads to features that used to work breaking. <\/li>\n\n\n\n
  2. Theme \/ Template \/ Block Editor \/ FSE Conflicts<\/strong>
    Themes (especially FSE or block themes) may not yet fully support The Events Calendar and its add-ons. Overrides, block assets, or template file paths might break. Plugins or settings related to template overrides may stop being applied properly. <\/li>\n\n\n\n
  3. Caching or Server Side Optimization Interference<\/strong>
    Sometimes caching (object cache, page cache, etc.) or optimization layers interfere with add-on behavior (filter queries, AJAX calls, REST endpoints). Events may be stored or loaded via new database tables, but caches still holding old logic can return incorrect or missing results. <\/li>\n\n\n\n
  4. Scripts \/ Asset Loading Errors<\/strong>
    If the add-on\u2019s JS or CSS assets fail to enqueue, or are blocked (by theme, plugin, or server rules), UI pieces may be invisible or broken. Sometimes block editor styles or assets are missing in the editor (Gutenberg) when features are activated. <\/li>\n<\/ol>\n\n\n\n

    How to Diagnose the Problem<\/h2>\n\n\n\n
      \n
    1. Check Plugin & Add-On Versions<\/strong>
      Ensure all TEC components (core and add-ons) are updated to compatible versions. Check       changelogs<\/a> for fixes.<\/li>\n\n\n\n
    2. Disable Conflicting Plugins \/ Themes Temporarily<\/strong>
      Test for       plugin and theme conflict<\/a>. Switch to a default WordPress theme (e.g. Twenty Twenty-Three) and disable other plugins except TEC and the problematic add-on. See if the feature starts working, this helps isolate where the conflict is.<\/li>\n\n\n\n
    3. Check the Fun\u00adctions \/ Template Overrides<\/strong>
      If you have custom theme template overrides for TEC or override files from the add-on, compare them with the latest version of the plugin\/add-on. Maybe functions\/hook names changed or new required parameters exist.<\/li>\n\n\n\n
    4. Inspect Caching & Server Optimizations<\/strong>
      Turn off object caching, page caching, any frontend cache, or server and CDN caching for testing. Confirm whether restoring behavior happens. Also check whether REST\/AJAX endpoints the add-on uses are being blocked or returning errors. <\/li>\n\n\n\n
    5. Look at Console Errors \/ Network Activity<\/strong>
      Use the       browser\u2019s developer tools<\/a> to see if scripts fail (404 errors, JS errors), or REST \/ AJAX requests return 4xx\/5xx or empty data.<\/li>\n<\/ol>\n\n\n\n

      Solutions & Best Practices<\/h2>\n\n\n\n