![]() |
did you go through the php file?
|
Explain...
|
Open bugs.php and replace vbugs.php with bugs.php
|
Every instance? So that means all my upgrades I'd have to do that? And I'd also have to edit the templates?!
|
Only when you upgrade this hack (if there is ever another update)
|
OK. I'll get right on that!
|
Just a note that I'm having some issues with this. I uninstalled it after designing my own bug reporting system, and for some reason the rows for the vBug settings in the usergroup editor still show up, just without phrases, and when I go to make changes to a usergroup I get a database error because it's trying to save vBug settings to a column that doesn't exist anymore. I can't for the life of me figure out where the settings table row is coming from or the part with that query. Any ideas?
Edit: Never mind. Damn bitfields... :p |
I have a forum set up to redirect to bugs.php. Members must log in again before using it.
|
Also I thought there was some sort of ntoification system built in?
|
Seems to be a bug with the moderation system. Even with the moderation option set to "Yes," all bugs submitted via vbugs.php are live for all users to see. I found a couple of issues in the code that address this. The vbugs.php is looking for the wrong option setting and bug moderation value, cleaning some global variables unnecessarily in the process.
Details for editing: Starting at line 650 in PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
|
All times are GMT. The time now is 05:02 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:
|