![]() |
as far as I can see this line
LEFT JOIN user ON (vbugs.userid = user.userid) should read LEFT JOIN user AS user ON (vbugs.userid = user.userid) at least it fixed the mysql error I got when I first called vbugs.php regards Tina ps. has to be fixed in 2 instances in vbugs.php |
I've tried that already but it didn't have any effect
|
Quote:
tina |
Quote:
|
Quote:
I guess I'd best drop the table prefix throughout the vB and start again from scratch eh? |
I have set general permissions in usergroups for those who can / cannot post to bugtracker.
but I would have liked to have kept it private using forum password or just using custom usergroup settings on that forum pointing to vbugs.php If i tell the forum to have password it is not applied. I can access the forum anytime even with password set. I cannot define custom usergroup settings either per forum. So it is not possible for me to exclude groups. Is this by design? Small example 1. I have guests set in default usergroup premissions as being able to add bugs/see bugs. For now i want to keep forum private for testing. So I edit the guest usergroup in that forum and change the forum permissions to custom and leave only view forum=yes, but turn off all other options (see others threads, post et all) I do not see any possiblity for custom settings for vbugs here. Guests can still see, post, add bugs without a problem! Small example 2. I have password set for forum to which points to vbugs.php. For now i want to keep forum private for testing. So I set password Guests can still see, post, add bugs without a problem! No password required. Possible I am missing something simple here? |
Ok...I'm back, after my cruise and the holidays I will start on the next version for those few little bugs. I am also going to complete the Pro version which can be obtained only from vbwar.com...
Next release will have all of the table prefixes redone.... |
Please let me know as soon as its out, and what paypal to use... glad ya had a good vacation.
if you need beta testers my team is very good at finding bugs... |
Here is a real bug:
When an admin chooses to make a bug 'private' when he is making a new bug, it doesn't make the bug private. You have to edit the bug after to make it private. Here is the solution to fix it: Find: PHP Code:
PHP Code:
Find: PHP Code:
Replace with: PHP Code:
For thouse who don't realize, the file I'm talking about is: vbugs.php |
When trying to do a search I get this error.
Code:
Database error in vBulletin 3.0.5: |
All times are GMT. The time now is 10:51 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|