Our site was affected by this issue, and we found this thread which discussed the issue and a "workaround".
I posted a question about this issue on the tapatalk site...this is what they said:
SnowDog said: ↑
you answered my question in your reply to my other post:
http://support.tapatalk.com/threads/...support.14954/
We have applied the patch as documented by the referenced thread and now tapatalk is working on our site again.
Thanks again for the help.
The actual workaround is posted here:
http://support.tapatalk.com/threads/...r-error.11732/
FYI, the developers of Valut Wiki claimed that tapatalk's implementation is the core problem and that this patch is a workaround. Did you folks at Tapatalk ever read this thread:
https://www.vaultwiki.org/issues/2871/
and evaluate their claims? It would be nice to have this problem solved in a way that does not require a patch. Seems like they have a fairly understandable position...perhaps you could work with them to understand the issue and fix the issue in your code, if in fact there is an issue?
Actually it is absolutely not a tapatalk issue, also we are unable to change our design as Tapatalk is different from other plugins, it needs to access almost all the native resources of the forum, acutally as all tapatalk forum owners know that we don't have such conflict with other mods. In fact, from our consideration, Valut Wiki dev team need to implement more rigorous code as this conflict was caused by that they are calling a php variable that does not exist, they assumed to be consider more when developing rather than taking the variable's existance for granted betwen two hooks.
Thank you.