View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000175 | HTML & PERL | Bug Report - Database | public | 2005-05-13 12:41 | 2007-12-06 08:28 |
| Reporter | DerIdiot | Assigned To | exp | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000175: disallow/change owneredits | ||||
| Description | owneredits are crap imho. lets make an example. person A creates a file with bad data person B makes a creq to fix it and the creq gets approved by a mod person A gets a note that his file got edited and changes it back WITHOUT A CREQ (aka owneredit) to his bad data, because he believes he's right. thats very bad imho and has happened more than once already. ok this leaves 2 solutions: 1. completely disallow owneredits or 2. allow owneredits only if there was no creq/modedit so far filed for this entry. I'm in favor of 2 as it still allows users to fix things themselves (like right after they added an entry they notice something wrong (typo, wrong codec choosen whatever)), but as soon as someone else confirms there was somethign missing/bad the owner turns into an average user and had to file creqs as well to change things. | ||||
| Tags | No tags attached. | ||||
|
|
option 2 all the way |
|
|
option 2 seems a good idea. it's not that easy to implement it though :| |
|
|
you can just add a new var to indicate if there was creqs to that particular entry and if yes, deny owner edits, ex: user A is still the owner but if there was a creq user A also goes trough the CREQ process to alter data. |
|
|
> person A creates a file with bad data > person B makes a creq to fix it and the creq gets approved by a mod > person A gets a note that his file got edited and changes it back WITHOUT A CREQ Person B will receive a note about it. So he could just warn the mods about it, and the mods will remove the ownership if required. I don't think your solutions are good, because they add a lot of creqs. I vote for leaving things how they are, and banning those who revert a modedit. |
|
|
-_- great someone is talking about things he has no clue about *sigh* the only one who could change the ownerrights is exp, who isn't every day available and if then only for a couple of h. besides thats a pretty bad idea anyway. >Person B will receive a note about it. So he could just warn the mods about it, >and the mods will remove the ownership if required. ahahahahahahahahahahahahaahahahahah oh sorry, but... ahahahahahahahahahaahahahahahahahahahah thats just too funny. users reporting such things is almost nill so thats a no go. and last, but not least why do you care about our workammount? it's us the mods who have to do that work. and no single mod disagreed with this solution so far! >I vote for leaving things how they are, and banning those who revert a modedit. ahahahahahahahahahahahahahah god damn you are funny... not. -_-; |
|
|
Option 3 maybe: Disallow owneredit when there is a change to a filled in field, rather than a change of a field from null state to data. Not that I think owner edits on already creqed files would be that much of an additional load. |
|
|
Option 4. Make him do a CREQ as everybody else. ;) EDIT: damn, option 3 was used. :P |
|
|
That's option 1 anyway, you massive tit. :D |
|
|
Well, I don't know if when they disallow edit then they can do a CREQ for that. Don't know how the system works internally so is better to say it. So, better be clear as not everybody knows how the MOD system works you clot. |
|
|
Please god fix this asap. =/ Solution 3: Disallow owneredit if: - Other user has an accepted creq for the entry (mod edits are creqs which are autogranted) - AOM has an accepted creq (even if it's the owner creqing) Probably useful: - Disallow owneredit of ed2k+size if more than one user has the file (has to go through a mod with explanation) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-05-13 12:41 | DerIdiot | New Issue | |
| 2005-05-13 13:13 | nwa | Note Added: 0000454 | |
| 2005-05-13 17:06 | exp | Note Added: 0000456 | |
| 2005-05-13 17:06 | exp | Assigned To | => exp |
| 2005-05-13 17:06 | exp | Status | new => acknowledged |
| 2005-05-25 10:18 | fahrenheit | Note Added: 0000481 | |
| 2005-05-26 18:36 | Amour | Note Added: 0000484 | |
| 2005-05-26 19:22 | DerIdiot | Note Added: 0000486 | |
| 2005-05-26 19:22 | DerIdiot | Note Edited: 0000486 | |
| 2005-05-26 19:23 | DerIdiot | Note Edited: 0000486 | |
| 2005-05-26 19:23 | DerIdiot | Note Edited: 0000486 | |
| 2005-05-27 11:43 | Rar | Note Added: 0000488 | |
| 2005-05-27 11:44 | Rar | Note Edited: 0000488 | |
| 2005-06-03 19:13 | DonGato | Note Added: 0000498 | |
| 2005-06-03 19:14 | DonGato | Note Edited: 0000498 | |
| 2005-06-03 20:12 | Rar | Note Added: 0000499 | |
| 2005-06-03 23:14 | DonGato | Note Added: 0000501 | |
| 2006-01-20 12:41 | petriw | Note Added: 0000723 | |
| 2006-01-20 12:42 | petriw | Note Edited: 0000723 | |
| 2006-01-20 12:44 | petriw | Note Edited: 0000723 | |
| 2006-01-30 12:47 | DerIdiot | Status | acknowledged => resolved |
| 2007-12-06 08:28 | epoximator | Resolution | open => fixed |
