vBcredits Collision Fix

[BlizzardHQ]

Staff Advise: You are strongly advised NOT to follow these instructions. For more info see post #2 & #5.

I been spending several hours with DarkWaltz to get this resolved.. Since it hasn't been posted here, I figured I would as I'm the one to push the bug fix

 
change the value in bitfield_vbulletin.xml from
 
<bitfield name="prefixrequired">131072</bitfield>
 
to
 
<bitfield name="prefixrequired">2097152</bitfield>

If you tryed to install vBcredits on a beta board as a clean install, you will first need to install the product after uploading the .xml change, uninstall it and reinstall it. This will get rid of the error in profile setting along with the collision error when trying to install any hack after the attempt of this one

[Wayne Luke]

I don't recommend changing standard bitfields. You should update the vBCredits addon so it doesn't conflict. Changing this will simply cause more problems in future versions. vBCredits should use its own bitfield for any permissions it wants to set, you should leave the default ones for the developer's internal use.

[BlizzardHQ]

Agree, but this was what he came up with until he has a chance to look into beta 3 more.

[PixelFx]

we'll update our mod and release it shortly for vbulletin 3.7...

[Marco van Herwaarden]

Thread moved, as this is not a modifiction.

Next if you have a bugfix for a modification, please post so in the modification thread. Starting a new thread does not help much.

Finally as Wayne already mentioned, this is the worsed possible solution (or better: symptom hiding) and will most likely lead to major future problems or it will break the current system.