Issue: Conflict with Tapatalk

See: http://support.tapatalk.com/threads/...r-error.11732/

I have already been in touch with Jayeley of Tapatalk and sent him an email in early August explaining the problem and possible solutions to the design issue in Tapatalk that causes this. Since I see in the thread that he says he never received such an email, I have just found it in my email history and forwarded the same response to him again.

Thanks! Still need the above workaround for now

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.

Hi,

This issue can be worked around from the VaultWiki side in VaultWiki 4 under vBulletin 4 only, since vBulletin 4 includes a class autoloader. From what I can tell, this issue should not occur in Tapatalk for vBulletin 3, which is good because there is no autoloader for us to use under vBulletin 3. If Tapatalk wishes to update their vBulletin 3 version to also skip init_startup, we will have a problem if they don't also provide us an autoloader to use.

For now we don't intend to fix this for VaultWiki 3, since there are no more expected releases for that version family. If we do release another update before VaultWiki 4, we will be sure to backport the fix to VaultWiki 3.

This is fixed in 4.0.0 Alpha 1 Chipmunk.

Originally reported for 3.0.19.

Hi I'm running a vbulletin 4 and have this problem too.

How do I get 4.0.0? In the members section I'm only able to download 3.x versions of vaultwiki.

Thanks

Version 4 is not a public release yet. Until then, you should use the posted workaround.

Where do I put the fix?

Thanks

AdminCP > Plugins & Products > Plugin Manager, VaultWiki plugin at hook "showthread_query"