vBug Tracker Lite 3.5.1

[Delphiprogrammi]

You mean this?


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



yeah this query



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



is there in the database (afteryou import the product xml)

while this one



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



will give a "values count don't match column count at row 1" error the attribute for the serialize column is missing in this query



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



would fix that note the bold part

[issa]

I'm not sure I follow your explanation, but I've tried replacing this query



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



with



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



but this still fails. Am I not understanding you?

[Zelda-King]

No the instructions were instead of having the script make the query, run it yourself in vBulletin's query manager.

[Noxious]

right ok, so far i have

Downloaded the file vBug Tracker Lite 3.5.1a.zip
Downloaded the file vbugs.php
Uploaded and extracted vBug Tracker Lite 3.5.1a.zip
Overwritten the original vbugs.php file with the vbugs.php file in this thread
Ran the product file and then manually entered the query



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



and i still getting the same errors


Warning: Invalid argument supplied for foreach() in /vbugs.php on line 570

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 575

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 580

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 585

what did i miss?

[murdo]

Ok, to clarify the process:

Downloaded the file vBug Tracker Lite 3.5.1a.zip
Extract vBug Tracker Lite 3.5.1a.zip

Edit "product-vBug_lite.xml"
- Look for line:



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



and replace with



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



Save the xml file.

Upload relavent files to your forum directory.

Install the "product-vBug_lite.xml" and you should be good to go!

(Too lazy? I've attached a fixed version of the archive!)

[Noxious]

yup now our vbugs works great, doesnt it murdo m8 :)

[murdo]

indeedy! great team effort :)

[Zelda-King]

Fixed here too, but just a note to others:

An XML upgrade (allow overwrite) doesn't fix it (not for me anyway). You need to uninstall the product THEN install the new version.

Backup the vbug tables and then when the product is reinstalled, select edit for one of your types/versions then save in order to update the dropdowns.

[Noxious]

Fixed here too, but just a note to others:

An XML upgrade (allow overwrite) doesn't fix it (not for me anyway). You need to uninstall the product THEN install the new version.

Backup the vbug tables and then when the product is reinstalled, select edit for one of your types/versions then save in order to update the dropdowns.

yes thats something we were unable to test as ours was a new installation

[Psionic Vision]

You need to uninstall the product THEN install the new version.

lol... But uninstalling the product erases all the data from the database. Which makes it pointless to use this bugtracker in the first place.

[Noxious]

Backup the vbug tables and then when the product is reinstalled, select edit for one of your types/versions then save in order to update the dropdowns.

may i point to the quoted highlighted part

[Psionic Vision]

Of course, but if there is a difference in table structure between the new and old versions, there could be a problem.

[Noxious]

ah stop crying your only moaning because you expect people to be ripped off by you, if you wanna upgrade from vb3.5 to vb3.6 and keep the bug system all you have to do is manually enter this sql code



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



otherwise if its a new installation, the altered files me and murdo did in this post (http://www.vbulletin.org/forum/showpost.php?p=1067801&postcount=255) are fine.

quite simple really isn't it much better than being ripped off $35 for one, wouldn't you say. Lets all boycot VisonScripts and shut this fool up once and for all, says everything about him his sig do not expect any of my free 3.5 hacks to become available on 3.6 anytime soon! get a life stop trying to rip people off

[Delphiprogrammi]

ah stop crying your only moaning because you expect people to be ripped off by you, if you wanna upgrade from vb3.5 to vb3.6 and keep the bug system all you have to do is manually enter this sql code



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



otherwise if its a new installation, the altered files me and murdo did in this post (http://www.vbulletin.org/forum/showpost.php?p=1067801&postcount=255) are fine.

quite simple really isn't it much better than being ripped off $35 for one, wouldn't you say. Lets all boycot VisonScripts and shut this fool up once and for all, says everything about him his sig do not expect any of my free 3.5 hacks to become available on 3.6 anytime soon! get a life stop trying to rip people off

hmmm "being ripped off" i use two scripts provided by visonscripts and i have never been ripped off.This bugtracker is nothing compared to the Vs bugtracker ...If he chooces not to update his free hacks that's his right nothing you can say about that.

[Zelda-King]

Of course, but if there is a difference in table structure between the new and old versions, there could be a problem.Possible. I haven't found one yet. What I do have is a cosmetic problem as reported in this post (http://www.vbulletin.org/forum/showpost.php?p=1028255&postcount=238). It looks alright when a new bug is submitted then goes awry (see attachment in link) when an admin edits/assigns the bug.

[Psionic Vision]

do not expect any of my free 3.5 hacks to become available on 3.6 anytime soon!

The reason I have that in my signature is because I do have a life and unfortunately, due to a variety of personal reasons that exist outside of the internet, this particular year have almost no spare time. I won't get into details as to why since you probably don't care anyway...

P.S. It seems that there is a slight difference between the datastore table in vBulletin 3.5 and vBulletin 3.6... Also, foreach is not just a cosmetic problem, but instead it a rather significant sign that there is a problem within the script, and that problem is causing an array of information not to be built properly. I wouldn't know the reason though since I am not the author of this script...

[alfaowner]

I get this every time I try to update the usergroups permissions:

Love to use this... any help out there... its ugp in field list unknown??

Database error in vBulletin 3.5.4:

Invalid SQL:
UPDATE usergroup SET

### UPDATE QUERY GENERATED BY fetch_query_sql() ###
`title` = 'Administrators',
`description` = '',
`usertitle` = 'Admin',
`opentag` = '<span style=\"color: #FF7D01; font-weight: bold; text-decoration: none;\">',
`closetag` = '</span>',
`passwordexpires` = '0',
`passwordhistory` = '0',
`pagerpermissions` = '13',
`pagerquota` = '100',
`pagerminpost` = '0',
`pagerminpostperday` = '0',
`pagermaxperday` = '10000',
`pagersendmax` = '100',
`pagersendmaxchar` = '500',
`forumpermissions` = '1048575',
`attachlimit` = '0',
`pmquota` = '150',
`pmpermissions` = '3',
`pmsendmax` = '100',
`calendarpermissions` = '63',
`wolpermissions` = '23',
`adminpermissions` = '3',
`genericpermissions` = '205520895',
`genericoptions` = '23',
`profilepicmaxwidth` = '100',
`profilepicmaxheight` = '100',
`profilepicmaxsize` = '100000',
`avatarmaxwidth` = '100',
`avatarmaxheight` = '100',
`avatarmaxsize` = '20000',
`advanced_bbcode_usergroup_on` = '1',
`advanced_bbcode_usergroup_permissions` = '121',
`advanced_bbcode_usergroup_permissions_custom` = 'a1024',
`googlemappermissions` = '1',
`vbugpermissions` = '7',
`ugp` = '0'
WHERE usergroupid=6;

MySQL Error : Unknown column 'ugp' in 'field list'
Error Number : 1054
Date : Tuesday, November 21st 2006 @ 08:51:59 PM
Script : /faqtests/admincp/usergroup.php
Referrer : /faqtests/admincp/usergroup.php?do=edit&usergroupid=6
Username : alfaown
Classname : vb_database


BTW - I installed this one as well, still get same error - vBug Tracker Lite 3.5.1a (with 3.6 support).zip

[midihead]

Been a while since last post. Any support still for this?

Thanks,

M

[midihead]

Any fix yet for the blank page issue? I get a blank page when I check the "subscribe" box and submit a message. This only occurs if I'm REPLYING to an existing bug, not when I post one.

I see others have experienced the same thing. Would be nice to have a fix. Also, it appears to be posting the reply, but twice. Any ideas?

One more thing: How can I set it up so that an Admin is notified every time a new bug or reply is posted?

Thanks,

M

[Psionic Vision]

This project has long been dead, you may want to check out vS-Bug Tracker instead. You can find the link in my signature.

[midihead]

This project has long been dead, you may want to check out vS-Bug Tracker instead. You can find the link in my signature.

Yea, I was afraid of that. I checked out your version and it looks great, but I can't seem to get ionCube working on our server. We installed some support and ticketing software that we gave up on after 2 weeks of hell with ionCube.

Cheers,

M

[Psionic Vision]

Yea, I was afraid of that. I checked out your version and it looks great, but I can't seem to get ionCube working on our server. We installed some support and ticketing software that we gave up on after 2 weeks of hell with ionCube.

Cheers,

M

Who's your hosting provider?

[tanyeri24]

screenshot or a working demo?

[Psionic Vision]

screenshot or a working demo?

Might want to read the last couple of posts. Esspecially post #270.

[Xplorer4x4]

Here is a port of my vBug Tracker hack from vb 3.0.x. This mimics the Bug Tracker found at vBulletin (http://www.vbulletin.com/forum/bugs35.php).
Quoted from second line of the post

[tanyeri24]

Might want to read the last couple of posts. Esspecially post #270.

But it was not your release, thats because I asked.. Anyway thanks for answer.

[ThomasR]

Psionic Vision: as i posted on your forum, no support for the attachment yet? It's a big problem for us to don't have this feature.

[Xplorer4x4]

Psionic Vision: as i posted on your forum, no support for the attachment yet? It's a big problem for us to don't have this feature.
You realize this is a completely different hack then the one PV makes right?

[chatzworld]

i only hve 1 major problem with this bug tracker, when a user goes to view bugs he/she can view ALL the bugs even if the bug is not theirs, now this is a MAJOR problem as you would not want users seeing stuff submited by other users aspecaly if its complaints!

how can i fix this?

[Xplorer4x4]

i only hve 1 major problem with this bug tracker, when a user goes to view bugs he/she can view ALL the bugs even if the bug is not theirs, now this is a MAJOR problem as you would not want users seeing stuff submited by other users aspecaly if its complaints!

how can i fix this?

Um it's not a bug, all bug trackers are designed this way.
http://www.vbulletin.com/forum/project.php?do=issuelist&projectid=6&issuetypeid=bug&appliesgroupid=7
As you see you can see all bugs.

[Psionic Vision]

i only hve 1 major problem with this bug tracker, when a user goes to view bugs he/she can view ALL the bugs even if the bug is not theirs, now this is a MAJOR problem as you would not want users seeing stuff submited by other users aspecaly if its complaints!

how can i fix this?

There is another hack that has a function of making bugs private. If you are interested, see my signature.

[LewisAinslie]

Yes but thats a payed mod, we need free mods

[DeMiNe0]

Not to mention YOU mod is dead too now. Now we really need a bug tracker.

[utw-Mephisto]

Not to mention YOU mod is dead too now. Now we really need a bug tracker.

Maybe people rather pay $50 for an official (and supported) one ?

[Darkwaltz4]

:D if any of you would like a new bug tracker to use, check out vBTracker...
http://www.vbulletin.org/forum/showthread.php?t=163094

[extremejoomla]

Getting a foreach error at the top of each page. On homepage get the following:

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 123

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 128

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 133

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 138

Not sure what the problem is - I am sure it is user error but can't figure out how to fix it.

Anybody help?

Thanks!
David

[Shawn Yue]

I Also having This Problem Vbulletin Message

You Do Not Have Permission

When I Go vbugs.php

Why LiKE THIS????

I WANT VBUGS.PHP

I RUNNING ON 3.6.8....

[LT Mote]

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 568

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 573

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 578

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 583

[joe1989]

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 568

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 573

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 578

Warning: Invalid argument supplied for foreach() in /vbugs.php on line 583

I Also having This Problem Vbulletin Message

You Do Not Have Permission

When I Go vbugs.php

Why LiKE THIS????

I WANT VBUGS.PHP

I RUNNING ON 3.6.8....

Might have something to do with the fact that this mod was released for 3.5, not 3.6, let alone 3.7!!

Make sure you find out if it's compatible before attempting to use, and then wondering why it doesn't work...

[Dark_Wizard]

I'll look at it and update this to work with 3.7 but give me some time.....

[Dark_Wizard]

vBug Tracker has been released here (http://www.vbulletin.org/forum/showthread.php?t=179589) for vBulletin 3.7 ;)