cykelmyggen

Customer
[DBTech] Facebook Style Status v1

As there is no supportforum in here for this mod I just wanted to say that it produces a " Error: service unavailable" in VbShout. Error dissapears when uninstalling so this is what I did to this mod for now. Pretty nice idea, though ;)
 
Last edited:
I just wonder if this is an official DBT mod as it doesn't occur in the lite download area or has a support forum? Still it makes my VbShout Pro stop working with the "service unavailable" message, and it isn't enough to disable it , I have to completely delete the Status-folder from server to get things running again.
Error message from VbShout Pro:
Code:
Invalid SQL:

                                        SELECT chatroomid, user.username
                                        FROM vbdbtech_vbshout_chatroommember AS vbshout
                                        LEFT JOIN vbuser AS user ON(user.userid = vbshout.invitedby)
                                        WHERE vbshout.userid = 5
                                                AND status = 0;

MySQL Error   : Column 'status' in where clause is ambiguous
Error Number  : 1052
Request Date  : Monday, June 7th 2010 @ 08:23:36 AM
Error Date    : Monday, June 7th 2010 @ 08:23:36 AM
 
Last edited:
It is, it's just such a small mod we didn't think it'd need support forums.
I'll add the Lite downloads and support forums with the upcoming v1.1 release, which I'll personally be overseeing :)

Have you tried the latest zip from vBulletin.org? It's possible that the 3.8 version was forgotten in the updated zip - it will be corrected for v1.1 anyway. But yeah, you do need to uninstall it before you can install v1.1.

Apologies for the FUBAR, it will be corrected within 24 hours :)
 
I downloaded the version called 1.0. some hours ago and reinstalled with the same, negative result. Maybe I'll just wait for 1.1. - but thanks for the answer anyway.
 
It's possible the vB3 version was not updated with the fix, then. We'll be releasing the update later today :)
 
1.0.1 was supposed to have the update for this, but v1.1 will definitely have the fix :)

I've completed the vB4 version, just need to do the vB3 version and then I'll push the releases / send update emails :)
 
Back
Top