The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
vBug Tracker 1.0.3 Details »» | |||||||||||||||||||||||||
You asked for it and here it is...a bug tracker that mimics the one at vBulletin.com.
There is no upgrade yet from the other bug trackers listed on this site but if enough people request it I will add it to the installer. Also, please DO NOT request help, assistance or ask questions via IM as I will ignore you and if your persistent will block you. Your best option for immediate support is at vbwar.com but I will check in here from time to time. Enjoy! Please click install if you use this hack. Support is only given to those who click. Thx! Version 1.0.1: Fixed missing phrase (here) Fixed redirect to blank page after edit bug Fixed assigned to not working after bug edit Version 1.0.2: Finally fixed the dropped title and missing phrases. Plus a few other small bugs you people didn't catch. New bug found...file updated. Users of version 1.0.2 need to perform these steps found here. Version 1.0.3: Fixed all tableprefixes and a small bug. Tested in both tableprefixed db and no tableprefix db... Pro Version can be seen here! Additional support can be found here. Show Your Support
|
Comments |
#132
|
|||
|
|||
as far as I can see this line
LEFT JOIN user ON (vbugs.userid = user.userid) should read LEFT JOIN user AS user ON (vbugs.userid = user.userid) at least it fixed the mysql error I got when I first called vbugs.php regards Tina ps. has to be fixed in 2 instances in vbugs.php |
#133
|
|||
|
|||
I've tried that already but it didn't have any effect
|
#134
|
|||
|
|||
Quote:
tina |
#135
|
|||
|
|||
Quote:
|
#136
|
|||
|
|||
Quote:
I guess I'd best drop the table prefix throughout the vB and start again from scratch eh? |
#137
|
|||
|
|||
I have set general permissions in usergroups for those who can / cannot post to bugtracker.
but I would have liked to have kept it private using forum password or just using custom usergroup settings on that forum pointing to vbugs.php If i tell the forum to have password it is not applied. I can access the forum anytime even with password set. I cannot define custom usergroup settings either per forum. So it is not possible for me to exclude groups. Is this by design? Small example 1. I have guests set in default usergroup premissions as being able to add bugs/see bugs. For now i want to keep forum private for testing. So I edit the guest usergroup in that forum and change the forum permissions to custom and leave only view forum=yes, but turn off all other options (see others threads, post et all) I do not see any possiblity for custom settings for vbugs here. Guests can still see, post, add bugs without a problem! Small example 2. I have password set for forum to which points to vbugs.php. For now i want to keep forum private for testing. So I set password Guests can still see, post, add bugs without a problem! No password required. Possible I am missing something simple here? |
#138
|
|||
|
|||
Ok...I'm back, after my cruise and the holidays I will start on the next version for those few little bugs. I am also going to complete the Pro version which can be obtained only from vbwar.com...
Next release will have all of the table prefixes redone.... |
#139
|
|||
|
|||
Please let me know as soon as its out, and what paypal to use... glad ya had a good vacation.
if you need beta testers my team is very good at finding bugs... |
#140
|
||||
|
||||
Here is a real bug:
When an admin chooses to make a bug 'private' when he is making a new bug, it doesn't make the bug private. You have to edit the bug after to make it private. Here is the solution to fix it: Find: PHP Code:
PHP Code:
Find: PHP Code:
Replace with: PHP Code:
For thouse who don't realize, the file I'm talking about is: vbugs.php |
#141
|
|||
|
|||
When trying to do a search I get this error.
Code:
Database error in vBulletin 3.0.5: Invalid SQL: SELECT DISTINCT vbug_severity.severityname, vbug_type.typename, vbug_version.versionname, vbug_status.statusname, vbugs.*, admin.username AS adminname, user.username, user.usertitle, lastreply.username AS lastreplyname FROM vbugs LEFT JOIN vbug_status ON (vbugs.vbug_statusid = vbug_status.vbug_statusid) LEFT JOIN user AS admin ON (vbugs.adminid = admin.userid) LEFT JOIN user ON (vbugs.userid = user.userid) LEFT JOIN user AS lastreply ON (vbugs.lastreplyuid = lastreply.userid) LEFT JOIN vbug_type ON (vbugs.vbug_typeid = vbug_type.vbug_typeid) LEFT JOIN vbug_version ON (vbugs.vbug_versionid = vbug_version.vbug_versionid) LEFT JOIN vbug_severity ON (vbugs.vbug_severityid = vbug_severity.vbug_severityid) WHERE 1 AND MATCH (title, description) LIKE '%test%' AND vbugs.vbug_typeid = '18' AND vbugs.vbug_statusid = '2' ORDER BY lastedit desc LIMIT 0, 20 mysql error: You have an error in your SQL syntax near 'LIKE '%test%' AND vbugs.vbug_typeid = '18' AND vbugs.vbug_statusid = '2' ORDER' at line 12 mysql error number: 1064 Date: Friday 07th of January 2005 01:43:20 PM Script: http://www.ezresources.net/forums/vbugs.php?do=list&s=&textsearch=test&vbug_typeid=18&vbug_statusid=2&vbug_severityid=0&vbug_versionid=0&assignment=0&sortfield=lastedit&sortorder=desc Referer: http://www.ezresources.net/forums/vbugs.php?do=list&s=&textsearch=&vbug_typeid=18&vbug_statusid=2&vbug_severityid=0&vbug_versionid=0&assignment=0&sortfield=lastedit&sortorder=desc Username: Aragorn IP Address: 160.136.49.104 |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|