![]() |
excuse me.. how do i import the xml detail? is this a plug in xml?
|
Quote:
|
Quote:
|
news,
aws is running on my 3.6.0 RC 3 system.Since these are my first tests the system isn't quite ready ready "enough" for a public release nut it's running good so far |
Great news Delphi! Great news.
|
Yes. Great news indeed. Cant wait for an updated release. This was the most valuable hack I had installed.
|
hi people,
I am building the admincp interface.I gotta start all over and build a product file in 3.6.x format (jelsoft changed some stuff in the products system)The phrases part needs some changes to since the phrasetypeid field is removed(phrases are identified through there fieldname)So far it's running good a MySQL error here and there but therefor i am doing tests to catch and fix them i changed the warnings field in the user table to warns because vbulletin's new infraction system also uses a field called warnings there (avoid conflicts) the sourcefiles will need to be updated to use the new field /me goes of to have a beer updated John, Wouldn't it be beter to just leave the "warnings" in place in the user table (and remove the code from the install / uninstall ) vbulletin only uses that field if you use the infraction system so to save some work (and have a system ready earlier) i'm *thinking* about this don't know if this is good through need some advise |
will this work on 3.5.4 ? or is there another Warnign system for 3.5.4 ?
|
Well, if vB is using one of AWS columns, you'd better create new ones. You never know if a user will activate both the AWS and vB's infractions together.
Also, maybe it is a good time to change the names in the program. I have found that some people get frustrated when "warned". Those types who ask you "Are you threatening me?" when you just tell them they did something silly or against the rules. Maybe we should change the "warning" to "ticket" ? I do not know, I can't think of another word. Also, one more thing. In the admin_warn.php, there is a small bug. Consider this situation: - a member has received a warning for 4 points. - the moderator who warned him made a mistake and issued the wrong warning type. - since the moderator is not very experienced he "removes" the warning and then issues a new one let's say for 3 points. - the administrator sees that and decides to completely remove the first warning, since it shouldn't be in the user's record. - The "Complete Remove" code removes the first warning, but also removes 4 more points from the user, thus the user ends up with zero points. In other words, the Complete Remove code does not separate between deleting an active warning and an inactive one. A small piece of code in the form of: Code:
if ($warn['warned_status']=='A') Another good idea is to change the wording for remove and complete remove. Maybe the "Remove Warning" should be renamed to "Mature Warning"?? Email me if you want to discuss these further. Rgds |
Quote:
|
All times are GMT. The time now is 07:30 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:
|