View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002354 | HTML & PERL | Bug Report - Interface | public | 2015-10-03 17:16 | 2016-03-11 21:37 |
| Reporter | Hinoe | Assigned To | DerIdiot | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Summary | 0002354: Tag admin, entities mode: entity row gets restricted class even though it isn't a 18+ entity. | ||||
| Description | In the tag admin page, entities mode, entity rows had the restricted class on them even though the entities weren't 18+. This issue showed up when I was removing a 18+-only tag from non-18+ entities, using the following link (it should currently be empty, but see steps to reproduce): http://anidb.net/perl-bin/animedb.pl?show=admin&adm=tags&mode=tagentities&reltb=animetb&tagid=2715&hentities=1 In the situation described, all 7 results I had at the time had the restricted class on them. | ||||
| Steps To Reproduce | Add t2715, which has the global 18+ flag and the is_porn_only flag on anime, to a non-18+ anime. This will ensure results for step 2. Look at http://anidb.net/perl-bin/animedb.pl?show=admin&adm=tags&mode=tagentities&reltb=animetb&tagid=2715&hentities=1 Verify the restricted class in the row. | ||||
| Additional Information | I believe the entity rows are taking the restricted class if the tag has tagdatatb restricted flag set to true, as opposed to the entity's own. I don't know whether the entity's own restricted flag plays any role on this. This may or may not depend on the specific tag system and on the specific combination of the statuses of the tag's and the entity's respective restricted flags. An alternative theory is that it depends instead on the tag system's is_porn_only and is_general_only flags instead of the tag's restricted flag, or in addition to it. | ||||
| Tags | No tags attached. | ||||
