I've just upgraded to 3.5.1 and now this isn't working, the permissions are gone from the usergroup menus.

Strange...let me get back to you as I will upgrade now myself.

It's the product thing that's wrong... If you change it to "vbulletin" it works fine...

on a whim I took a look at the bitfield file for this hack, and another one thats working right, the product listed in this hacks bitfield is "vbugs" the one for the other is "vbulletin".

I made the edit and it works now.

Can this support multiple products? :) Or just one...

I need one that can support multiple products.

I changed my product to vBulletin in the drop menu, yet it still does not work. No setting show up in user group nor are am I able to access the script. It gives me the typical permisions message.

i had the same problem

to solve it
just edit the file bitfield_vbug.xml under /includes/xml/

and change
to

forgot to mention that it's only happen when installed it on vb 3.5.1

Wouldn;t it be easier to just change it in the vBug options? the option for version was set to vBug, so wouldn;t changing the version to vbug work alot easier? ;)

Also I think i can find this myself but if not, I want to change a few of the options in the drop down menu. For example There is no need for members to have Admin CP has an option lol, so I want to put an if condition around it for admins to see, not members. Plus I want to add an option or two.

In /admincp/vbugs_admin.php (~Line 63)

find:
change to:

I found a small bug:

I added an additional usergroup and set this group as secondary group to some of my users.
Those users should be allowed to administrate bugs.

I gave the rights to that group but it is not working.
I cannot select people from this group to assign them calls.

It is working when I make this group a primary usergroup but I can't do this.

Please Dark_Wizard, how can I make also Secondary Usergroups work?

I keep getting the below error when I do the "Add/Import Product" step. I did have the vBug Tracker 1.0.3 for vb 3.0 previously.

Any ideas?

There wasn't an updater included with this thus your error. Contact me via IM and I will help you through removing the old version so you can install the new version.

I will look into this....

I have just upgraded to 3.5.1 and the uptions under User Groups to set if members can see/add etc. bugs have vanished.

I checked and the bitfield_vbug.xml file is in the includes directory. I have even re-imported the Product but still nothing.

Upgrade coming in about 15mins....

New version released, sorry for the delay as I have been very busy lately.

The user group permissions have appeared ok, but I am getting this error message when I go to vbugs.php:

Database error in vBulletin 3.5.1:

Invalid SQL:

SELECT userid, username
FROM user
WHERE usergroupid IN(5,6)
OR FIND_IN_SET(5,6, membergroupids);

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 ' membergroupids)' at line 4
Error Number : 1064

One sec...looking into it. Stick around

I may have to catch your next update in the morning. I have the Flu, it is 12:23 am here and I have been working for the last 16 hours; so I don't know if I can keep my eyes open much longer.

Ok...here was the issue, I wrote the coding for PHP 5.x/MySQL 4.x and forgot about backward compatability. It is now fixed so you can now download the new file.

I cannot assign anyone bugs if they have more than 1 secondary usergroup. I've created a usergroup so they can administer bugs, but if they are assigned to another one as well, it doesnt work.

Also, is there a way to edit a bug and leave it unassigned?

Many thanks. Installed and working as designed.

Hi Dark_Wizard,
any update on the PRO Version?
I've been checking your site and the pro version features are much better

So your saying you have more than one usergroup/secondary group that has admin rights to bugs?

You can edit the bug in the admincp.

Due to the extent of the features in the Pro version this is taking longer than anticipated, just keep checking the site as I won't commit or comment on any dates.

will do :)
so far our user are enjoying the lite version and making life easier on our website

Here is an example of a user on the board

they usually have their primary usergroup as registered users
Secondary usergroups are based on what forums they can view, some can have as many as 5 or 10 different ones.

I currently have the administrator usergroup and a second one that can administer bugs. What I found is that if I put someone in that second group, and they have other secondary usergroups, they wont be able to be assigned to a bug. However, if they don't have another secondary usergroup they will be able.

Ok...will look into it.

For what it is worth, I have the exact same configuration as timmed (although I have been still holding out actually running this on my live server).

Hi Dark_Wizard,
when you have a moment could you have a look at the subscription code on the 3.5.1 version.

When a user tick the subscribe box and post a reply to a bug, instead of showing the reply to the bug it goes to a blank page and no subscription are placed in the user subscription.

Cheers

Mone'

i get the same thing. no subscription and a blank page. though the reply gets posted (at least in my case).

same here, the reply get posted but it confuse the hell out of my users :P

Yep, I meant to post that too. I don't get notified when a new reply is posted.

Will do...

I'm also happy if you release your pro paid version............. hint , hint ;P
Cheer for the great hack

Looks great - looking forward to seeing the pro version. One fix for bugs.php:

Also notice an empty <span> tag in list template that is unecessary.

Probably not a bug, but seems if you edit a ticket, it assigns it to the first person in the dropdown, not leaving you the chance to leave it unassigned.

Thanks for the find, fixed and file updated.

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 edited everything, will I know have to reedit it?