vBug Tracker Lite 3.5.1

[high]The XSS security flaw reported in this modification has been fixed by Staff and a new zip file (3.5.1a) uploaded.[/high]

Here is a port of my vBug Tracker hack from vb 3.0.x. This mimics the Bug Tracker found at vBulletin.

Details:

• 7 - table additions
  96 - Phrases Added
  3 - file additions
  2 - xml files
  8 - template additions
  3 - Plugins

Please click install for support! For those interested, the Pro version is in development and should be out soon. It will be released at vb-scripts.com.

Sept 25, 2005
Bug fixes:

• * Added Missing phrases for editing status, type & severity.
  * Fixed bug in changing displayorder

Sept 26, 2005
Bug Fixes/Changes

• * Fixed bugcache issue and tested
  * Added admin usergroup permissions

Sept 27, 2005 (Part 1)
Bug Fixes:

• * Fixed subscribe issues and missing phrases.

Sept 27, 2005 (Part 2)

• * Complete rewrite of the subscription piece including the unsubscribe.
  * Subscriptions fully tested and working from all aspects!

Nov 7, 2005

• * Fixed missing table prefix when editing status.
  * Fixed issue when editing severities.
  * Now supports secondary usergroups.

Nov 24, 2005

• * Fixed extra span tag in list template.
  * Fixed searching on version.
  * Added "unassigned" to dropdown.

Jul 11, 2006

• * XSS Flaw fixed by Staff.

To upgrade:

Import the product xml and select "Allow Overwrite".
Upload all the files overwriting the old ones.

Lastly... Please follow the instructions exactly as they are outlined in the documents/install.txt and in the order as listed to avoid any problems.

Updated for vBulletin 3.7, Get it here

[Dark_Wizard]

Originally Posted by The Wise One

thanks for the update. did you have any luck with this by chance?

https://vborg.vbsupport.ru/showpost....&postcount=152

and i keep getting this error when ever i try to edit a bug. it only appears when i submit the edit. it doesnt appear to affect anything as the edits are applied...but it continues to pop up.

line: 429
char: 2
error: 'document.cpform.description.value' is null or not an object
code: 0
URL: vbugs.php?do=edit&vbug_id=(X)

the id in the vbug doesnt matter as it happens regardless of which bug i try to edit.

I cannot reproduce this, please give me the steps in which you followed to produce this.

[Dark_Wizard]

Originally Posted by King Kovifor

I edited everything, will I know have to reedit it?

Can you tell me what you edited so I can guide you?

[The Wise One]

Originally Posted by Dark_Wizard

I cannot reproduce this, please give me the steps in which you followed to produce this.

subscribe problem

1. click on "Submit New Bug".
2. fill in the fields (from top to bottom).
3. tick the "Subscribe" box.
4. click submit.

popup error

1. click on any bug from the list.
2. click on "Edit Bug".
3. make any change (series of changes...doesnt matter).
4. hit the submit button.

[Dark_Wizard]

Originally Posted by The Wise One

subscribe problem

1. click on "Submit New Bug".
2. fill in the fields (from top to bottom).
3. tick the "Subscribe" box.
4. click submit.

popup error

1. click on any bug from the list.
2. click on "Edit Bug".
3. make any change (series of changes...doesnt matter).
4. hit the submit button.

Are you doing this as an admin or end user?

[Todi]

One thing i miss is the ability to edit/remove responses. Is that intended for the "Lite" version at all (or have i missed it somewhere?), or do i have to fix it myself?

[King Kovifor]

I Changed it from vBug.php to bugs.php - and the templates to inlude that.

[Dark_Wizard]

Originally Posted by King Kovifor

I Changed it from vBug.php to bugs.php - and the templates to inlude that.

Why?

[King Kovifor]

That's what the owner wanted, and it's currently down... so no big rush.

[The Wise One]

Originally Posted by Dark_Wizard

Are you doing this as an admin or end user?

as an admin. no other usergroup is setup to admin bugs.

[OneShot]

Nice Hack - clicks Install. One thing tho, and that has been mentioned before - Users who have more then one secondary Usergroup don't show up as expected in the "To Assign" Dropdown box. Only if they are selected as Primary Users for the Usergroup who can admin vBugs. And out of whatever reasons the cpnav_vbug.xml did not work with my ACP. I did some little fixes and now everything is perfect and works.