Version: 1.0.3, by Dark_Wizard
Developer Last Online: Jun 2014
Version: 3.0.6
Rating:
Released: 09-17-2004
Last Update: 02-20-2005
Installs: 97
DB Changes
No support by the author.
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...
Adding Table vbugs
Adding Table vbug_response
Adding Table vbug_severity
Adding Table vbug_status
Adding Table vbug_subscribe
Adding Table vbug_type
Adding Table vbug_version
vBug Tracker Tables Added!
There seems to have been a slight problem with the Lineage 2 database.
Please try again by pressing the refresh button in your browser.
An E-Mail has been dispatched to our Technical Staff, who you can also contact if the problem persists.
We apologise for any inconvenience.
help
View the source of that page, copy and paste it here which will give me more details...
One thing though, when you edit a bug to update its status etc, it redirects to a blank page and when u check what it updated, it updated the bug status but didnt update the assigned to bit and it also deletes the bug title.
One thing though, when you edit a bug to update its status etc, it redirects to a blank page and when u check what it updated, it updated the bug status but didnt update the assigned to bit and it also deletes the bug title.
Hmmm.....Is this on the front end or admincp? I don't see that here so I need to know.
I just tested on Natch's site and see no problems in the front end or the backend...please provide me details as outlined above.
Invalid SQL:
SELECT userid, username
FROM user
WHERE usergroupid IN()
mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 3
Invalid SQL:
SELECT userid, username
FROM user
WHERE usergroupid IN()
mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 3
mysql error number: 1064
As outlined in the instructions at the end it states "You will also need to set the vBug Tracker Permissions in each usergroup that uses vBug Tracker", this error is indicating you have no admins setup for vBug Tracker. Please do this and the error will not occur again. I will add some error checking in the next version.
When i enter a bug and click subscribe i get an e-mail saying
Could not find phrase 'vbugs_new_subscribe'.
What should i do to fix it?
Create a new phrase in the "Email Body Text" phrase group called vbugs_new_subscribe and add the following text:
Code:
Hello $username,
You are now subscribed to the following bug - $title.
$vboptions[bburl]/vbugs.php?do=view&$bug[vbugs_id]
Yours,
$vboptions[bbtitle] team
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unsubscription information:
To unsubscribe from this bug, please visit this link:
$vboptions[bburl]/vbugs.php?do=unsubscribe&vbugs_id=$bug[vbugs_id]
Please click install to obtain any further help....thx!
Hmmm.....Is this on the front end or admincp? I don't see that here so I need to know.
I just tested on Natch's site and see no problems in the front end or the backend...please provide me details as outlined above.
Its on the front end, it doesnt give me an error just a blank page.
I looked in the vbugs.php file and it seems the code for "Update Bug" is different from the rest.