That's good to know, some people would be very upset to lose their thanks count.

A hotfix version has been released to fix all outstanding known issues.

To upgrade, follow the normal procedure when updating a product.

- DragonByte Tech Development Team

vBActivity & Awards v2.1.3 has been released.

This version brings not many visual changes, but significant back-end changes.

• The Installer and general code has been refactored to be more in line with newer DBTech products. This should eliminate some white page problems people were experiencing with the Bitfields / Permissions.
• Temporarily removed [DBTech] Advanced Post Thanks / Like support. *
• An API has been created to allow other modifications to more easily integrate into vBActivity.
• Added support for an upcoming Postbit Tabs mod.
• Turning off the automatic postbit display (as required by the Postbit Tabs mod) no longer hides the content even with manual placement.
• Profile Tabs now look good on both vB 4.0.8+, and earlier versions.

* Will be re-enabled over the past couple of weeks with an update to Advanced Post Thanks / Like v1.1.x

IMPORTANT!!!
If you receive the following error:
Fatal error: Call to a member function fetch_activity_level() on a non-object in [path]/dbtech/infopanels/includes/hooks/forumhome_complete.php on line 175
Please re-download InfoPanels and re-upload all its files. Support for the new vBActivity code structure was added 3 days ago in the hotfix that was released then.


Fillip

Actually, I'm getting

Unable to log into my Admin CP at the moment.

Updated zip, try now :)


Fillip

Okay, I'll try it out. It turned out that it didn't like the Quick Links/Community Links and Navbar Tab features enabled. When I turned them off, it seemed to work.

Seems to have corrected the problem. Thanks. (And thank goodness for define('DISABLE_HOOKS', true); )

Because we code our modifications on vBulletin 4 and then back-port them to vB3, we use an emulated vB4 template engine when vB3 is detected in order to allow us to release identical files for both versions.

This severely cuts down development time. However, because all our modifications use this method, it only takes one other modification to be active in order to not trigger that error.

That's why sometimes, that error slips through the cracks :(


Fillip

Quality mate, quality!

I see you updated it again since yesterday. Was it just a minor fix, or should I update again?