Quote:
Originally Posted by Revan
I had hoped I could just edit my post but meh gotta bump it now 
I am in the process of installing this hack, and I must say I don't like having a table of its own for the warning_options. Im in the process of creating $vboptions for it all, then edit every part requiring this query to use $vboptions instead.
If you want, sv1, I can write up an installer part for adding into the datastore to help reduce query load for this hack (having 1 extra query ran every time I access the ACP just wont do for me  )
EDIT: I am in the process of cleaning up the files, and this will be one of the issues I am fixing.
If you want, sv1, I can send you the files once Im done cleaning them up. It will be issues like the one quoted here, plus coding style I will be tampering with, Im not trying to make my own version of this 
|
Raven,
Your idea of using $vboptions is a solid one, I didn't think of that, as I used ZT's original structure and I just used that table for my hack as well. The query for the options is indeed a pain. I wish I had thought about it, because now, I have to go back and edit all the files (not too ddifficult) and all the templates (gosh I hate that)! Darn!!!
And indeed, the code needs some cleaning work. Now that I've finished installing the other hack I mentioned above (the Inline Moderation Hack, great one), I think I'll spend some time cleaning up the mess.
Of course, your help is welcome, don't forget I started this from ZT's code, so a lot of the code is not mine either. An installer which will take into consideration the styles thing would be a great help, as I do not have any additional styles and I can't even help users with this issue. I just do not know how to handle them.
As for the Yes/No/Yes thing on the drop down menus, I am not sure I can do something about it, I am using vB's standard method, and that's how they show up after you set the value once.