Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Warnings are difficult to keep up with. I think it should be clear to the person receiving warnings that they are... receiving warnings.
My suggestion is a simple moderator control on every post in the form of a WARN button. Upon clicking the button, the moderators will have a variety of icons representing rules that were broken, such as:
Flaming
Spam
And more. They choose one, select it, type in an explanation into a box, and the icon will appear somewhere on the post. When users click that icon, the explanation will appear.
In addition, users will be able to search for their own warnings with a new search function.
edits:
After submitting the form, the warning info automatically goes into a warning index for the mods and admins to see, or summat like that.
Last edited by Chimi (Jul 27 2011 4:56:03 pm)
Offline
I like it! I think this would work out great
OFF-Topic; the bottom of the flame looks like, well, you know.
Last edited by BuzzerBee (Jul 25 2011 8:22:40 pm)
Offline
Great idea! It's perfect!
nice idea! But I don't know if they could add that :/ I'm pretty sure they can't
Offline
nice idea! But I don't know if they could add that :/ I'm pretty sure they can't
Cyclone owns forumify, he can do anything. Plus we have jakery, who made the gravedig/double post warning system. I'm pretty sure its possible.
This sounds like a good idea, would be very helpful
So it would be a bit like the report thing. Like it, but I don't see much of a difference for us users. I think we should get e-mailed every time we get warned with the post(s) we f&#ked up on and why. That way, even if we get banned, we can see where we went wrong.
Offline
You do have a great idea. The issue isn't whether it can be done, but:
1) Designing/coding:
A new warning system is much more complicated to create than the gravedig/DP caution.
2) Programmer availibility:
The caution took a day to create; this feature could take weeks. I can't speak for Cyclone, but I have much less free time than I did a few months ago.
3) Affecting other Forumify boards:
If you change the code that runs ee.forumify.com, you change the code that runs every forumify.com board. We got away with this for the caution feature because the change is invisible unless you include the Javascript file I wrote, which Cyclone put into the EE Forum theme.
4) Testing/Support/Maintenance:
Another big difference between the caution and this proposed warning system is the caution system was purely cosmetic; Nothing about the forum program flow was affected when we put the caution feature in. If we build this new system, we have to test, retest, and test again to make sure the warning feature works correctly, doesn't introduce any new bugs (which it will; Murphy's law), and doesn't crash the forum under any/all conditions. Also, since this would be new code for a new system, somebody would be expected to maintain and improve the code as time goes by.
I'm not saying it can't/shouldn't be done, but this is a relatively huge change for the forum, and we need to give the idea serious thought before deciding to move forward.
If I knew how to do it, I would.
Maybe mods could just edit in the BBCode?
Seriously? I don't know any coding whatsoever, but if this is a huge change, I don't know how anything ever gets done with this forum.
I hate tall signatures.
Offline
But you don't know how the current warning system works. Right now there's no warn or ban button on a post. It's all done on the user's profile.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
I knew that.
Well, that's quite a strange warning system. It needs to be changed to be more informative anyway. Does it require you to input a link to the post for reference? It should if it doesn't.
I hate tall signatures.
Offline
FluxBB has no built-in warning system. All of our warn notes and bans are submitted by hand; there's no convenient "warn" button or form to fill out. Issuing warnings is a real chore, tbh.
The huge change is invisible on the web side; it's all in the PHP code and databases. We are talking about significant alterations to several PHP files, several new database queries, and to top it off, building a new "warnings" database table from scratch. (and possibly some new support tables, as well).
And keep in mind that coding is a very strict, painstaking practice. If you screw up any minor detail, you can break your entire site. So we would have to spend loads of time testing and debugging the new code, all without breaking the live forum.
My point is, coding and deploying a new warning system might be more trouble than it's worth. :/
I guess you'd have to consider if it'd be finished in time to be relevant, if EE'd still be popular, then. If it was implemented all over forumify, I think it'd be worth it, though. That's cyc's business, I suppose.
I hate tall signatures.
Offline
Guess what. I just bought a book - pretty much the entire encyclopedia of knowledge on HTML, XHTML, CSS, JavaScript, PHP, and MySQL database stuff.
>:O TONIGHT WE'RE GOIN' HARD.
I hate tall signatures.
Offline
cool, yeah thats cool chimi
Hey, that's me. The cool kid reading his 1100 page Web coding book with the pocket protector filled with nifty pens.
Pages: 1
[ Started around 1738658444.6795 - Generated in 0.249 seconds, 12 queries executed - Memory usage: 1.55 MiB (Peak: 1.72 MiB) ]