Unreliable Output from Module-Defined Smarty Functions

[aquaticwe]

I'm seeing intermittent bugs where a module's custom Smarty tag, when called multiple times on the same page or in different Global Content Blocks (GCBs), sometimes outputs the cached result from the first execution instead of recomputing based on the current environment or input parameters.

A tag like {my_module_data item='A'} outputs the correct result. Then, on the same page, {my_module_data item='B'} still outputs the data for item 'A'. This most commonly happens when a tag relies on an external Smarty variable or $gCms->variables call that has been modified since the original execution, but the module's Smarty method appears to be executed using the original (old) variable state.

[DIGI3]

Do you have "Enable Smarty Caching" enabled in admin preferences by any chance? (this typically never goes well unless a lot of steps are taken to prevent issue)