Wutime
Well-known member
Yes, this explains why I never ran into this issue locally, it's only generated if there's an error on the thread. My local setup rarely has these types of scenarios because it's a clean install. I'll have to consider this in the future to ensure I catch more edge cases.@Wutime Since upgrading from v1.7.2 to v1.8.0 XF2.3.6 this error is generated when an error is generated. If I disable the addon XF captures the error with my standard error message. Thoughts? How can I redownload v1.7.2?
I'll release the update now.