The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
[HTL] & [TXT] Request/Bugs Tracker (formally vB-Bugs) Details »» | |||||||||||||||||||||||||||
[HTL] & [TXT] Request/Bugs Tracker (formally vB-Bugs)
Developer Last Online: Jan 2011
Request/Bugs Tracker
Version: 1.0.0 vB-version: 3.0.0 Developer: ^BuGs^ (Shane on vB.org), ixian, and Kirby (Original) Install difficulty: Easy File edits: 1 Template edits: 0 Description of the Hack: This is a basic vBulletin-powered Request/Bugs Tracker like the one on vBulletin.com HACK INSTALLATION DETAILS: New files for this Hack: bugs.php admincp/bugsadmin.php Files modified for this Hack: admincp/index.php New templates for this Hack: bugs_search_no_results bugs_addbug bugs_addbugnote bugs_listbit bugs_bugnote bugs_details bugs_list BUGS New DB tables for this Hack: bugs bugnotes bugtypes bugseverities bugstates Read the readme.txt file if you are updating from vB-Bugs!!!! As of 4/17/04, 9:21am EST Fixed: Warning: Invalid argument supplied for foreach() in /home2/bear/public_html/forums/includes/sessions.php on line 262 - vvbugs_settings.xml (new exported data from the HTL generator) Fixed: https://vborg.vbsupport.ru/showpost....4&postcount=22 (add the function inside bugs.php to help it cashe the bugs types everytime you load the page if a new one is not in the list. Updated: readme.txt (a few grammer issues that I overlooked.) As of 4/17/04, 9:47am EST Fixed: bugs.php where if you edited a bug report and left the assigment to "unassigned" it owuld stop. This is now fixed where it will stay at unassiigned. As of 4/20/04, 1:38am EST Fixed: bugsadmin.php had had a program with the "add" and "edit" fuctions. Sourceforge.net - New home for this hack under the direction of the group "vBulletin Modification Packages". Visit us at: https://sourceforge.net/projects/vbmodificatiopk/ . (Best place to post bug reports. Ironic isn't it?) Show Your Support
|
Comments |
#32
|
||||
|
||||
Quote:
I was thinking more like "x new bugs since your last visit" but this is along the same lines, and yes it'd be easy to do. Right now, on my side of things, I am working on the hide/show closed bugs, color-coding bugs by state (i.e. critical bugs red, moderate blue, etc - this is a feature found in just about every other ticket system out there and it makes a huge difference when you are trying to prioritize a lot of bugs) and the big one, email notification, which IMHO is the one major feature this hack has always lacked. If you want to do a simple mod to do the above then by all means please do, especially if you've already done it. We're not credit hogs here; we just want a good hack to get even better and if you have something useful to add don't let us hold ya back |
#33
|
||||
|
||||
it's actually workin fine for me. Except sometimes, when I add a bug, i mess aroudn with the options and I can't add it. All i get in the confirmation page is a table strip. Oh well, good job!
|
#34
|
||||
|
||||
boho, try clicking on 'Make new settings Volatile?' in HTL. That forces the script to do it's stuff.
|
#35
|
||||
|
||||
I don't use HTL. Never did and never will.
|
#36
|
||||
|
||||
Quote:
|
#37
|
||||
|
||||
boofoo, how do you update the settings? Cause I uninstalled HTL on my live forums and I can't get the XML uploaded. All I know there is a way how and I don't know
|
#38
|
||||
|
||||
Allright. I am going home this weekend (at college). I thnk I fixed all the major errors for now. I am hoping by the time I get home the CVS repository has propergrated. Untill then, I will have to make my changes untill I get back monday night (late).
I know this is bad saying this, but if you are having major problems don't use it right now cause I won't be able to do anything till I get back. Sorry. |
#39
|
||||
|
||||
I uninstalled it all until the xml problem is fixed. Keep me posted.
Just do an install file all in one shot instead of the 3 xml files. |
#40
|
|||
|
|||
Just installed everything brand new, and I got this error when I tried to go to Request/Bugs Tracker Types in my AdminCP:
Parse error: parse error in /home2/volvinet/public_html/forums/admincp/bugsadmin.php on line 75 Also when I go to bugs.php I get thie at the top of the page (before my header): Warning: Invalid argument supplied for foreach() in /home2/volvinet/public_html/forums/bugs.php on line 138 Warning: Invalid argument supplied for foreach() in /home2/volvinet/public_html/forums/bugs.php on line 144 Warning: Invalid argument supplied for foreach() in /home2/volvinet/public_html/forums/bugs.php on line 150 |
#41
|
||||
|
||||
Quote:
PHP Code:
to PHP Code:
PHP Code:
like if the for statement was an if statement. Stupid mistake As for the second error, I don't see how that can be possaible. The "cashe" is built before those lines are even ran. Try the bugs.php file again. At the top of the file should just be $Id$. Going to put in revesion tags so I can keep track of what people have. @ixian: What is your SF username?! |
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|