Issue: Posible Conflict with Syndol's bookmark addon for xenforo

I don't see how the install process itself would cause this. The process adds things but doesn't remove anything. It's possible that your mod uses a monitoring system to detect when something is deleted, rather than extending the delete method in the DM for the item, and that the monitoring system may have been turned off during the VaultWiki installation. Without knowing more about how the mod works, I'm afraid we cannot debug this and it is a paid third-party add-on.

Well it did.

A more helpful response would include information about how the mod you mentioned detects when a bookmark's resource is removed. As stated above, without knowing that information, we cannot even begin to figure out why it would be affected by VaultWiki's install process, which itself only adds new data to the database.

Yeah I know. I am just letting you know. I am not going to go through the install process again. But I notice you have some sort of bookmarking feature so I let you know. 99% of all mod conflicts in XF are usually caused by two mods not following the naming conventions as outlined by KAM. "bookmarkThing" would be wrong while "vaultWikiBookmarkThing" would be right and not likely to conflict. I notice you use vw a lot which is not as unique as vaultWiki.

Yes, we're aware of that vector for conflicts. There are a few items that need to conform to the vw convention that don't currently, but I don't believe they are DM or bookmark related. As far as I know VaultWiki 4 doesn't have social bookmarking at this time, but it is a feature request.

As far as the conflicts, I've gone through and fixed a few places that were extending through XFCP that still needed the vw prefixing. However, I still can't fix a bunch of stuff in the Parser and Formatter classes. These use generic property names that exist in vBulletin but don't exist in XenForo, and those could be a vector for conflict. Fixing that will require a major refactoring of the parser system across all forum platforms since the names are all shared and a lot of them are public to other classes.

I'm thinking I will have to implement a &vwData function on every parser-related class in all platforms, implement wherever direct property access is used, and use it to translate property names (model, instance, parser, for, item, et al are all unprefixed).

This was for bookmarks in the resource manager only in case I wasn't clear enough. Forum bookmarks were fine. Perhaps if you don't have a copy of the RM it's just something you won't see. I had no problem re-adding the bookmark and it's still there now. I haven't loaded gamma 2 yet so no idea if that affects it.