41
           
            
                
     
    
    Aubrey:
I have both good and bad news 

The good is I think I found the cause for this error, *I think* it is related to Module Caching in XOOPS template engine (Smarty), so if you disable caching, it may just go away.
The bad news is I still don't know how to fix it, 

 but I'm currently looking at it.
I'm looking to confirm if this is the cause. And I can't reproduce your error on my site even after turning Module cache on. 

Could you please turn caching off for this module, test it and let me know?