| #1476 by genuineparts 2023-01-06 at 22:28 | < report >I personally feel like implementing a field that relflects the status of a Producer would make sense. I.e. We know that Solpress is defunct and Lose is gonna shut down as well. So A field for Producers indicating (Active/Defunct/Renamed/Unknown). Any input for/against? |
| #1477 by shinytentacool 2023-01-12 at 11:04 | < report >BBcode buttons would be nice |
| #1478 by slashslayer 2023-01-13 at 14:48 | < report >i don't know for how long the "card" and "grid" views have been available for VN lists, but thank you very much for them mr. yorhel 🧎 just a question: is it possible that the notes will also be displayed in those views in the future? |
| #1479 by Yorhel 2023-01-13 at 15:19 | < report >Your notes are totally not going to fit in those views and the layout isn't flexible enough to accomodate. Truncated notes are possible, but not sure how useful that'll be. In any case, clicking the list status icon will open up the popup thing which has your notes. |
| #1480 by Ileca 2023-01-13 at 15:44 | < report >Are you f****** kidding me?? Grid is available for your lists?? OMG but it's true! ?(°Д°≡°Д°)! Sasuga Yorhel and his sneaky updates smh... also his love of undecipherable tiny icons... |
| #1481 by bassttark 2023-01-17 at 16:59 | < report >#1474 If you are considering separating the spoiler override setting and the highlighting setting in the Tags and Traits profile, I suppose that would mean that a "Show as default" option would be added in the spoiler override dialog (showing the tag according to its usual spoiler level). This would be great because I could use this feature to "whitelist" some children tags that I want behaving as default even if I have set another override setting for its parent tag. By the way, while separating the highlighting setting, it would be awesome if we could select its highlighting color from a few different color options. |
| #1482 by Ileca 2023-01-29 at 20:55 | < report >Please sort the staff in edit forms not by ID but by role (order of importance) > staff name (alphabetical) > note (alphabetical)Last modified on 2023-01-29 at 20:55 |
| #1483 by Mario3573 2023-02-08 at 21:51 | < report >Could native resolution VN covers be implemented? As in they would work like screenshots where you see the current small version then can click on it to see it in it's native resolution, would be useful to have a source of high resolution cover images for VNs, as some are pretty hard to find. Also could be good to be able to upload every cover for a VN in a separate tab or something, and then just select a main one for the page, but that's a separate suggestion. |
| #1484 by rampaa 2023-02-19 at 17:24 | < report >Would it be possible to make link respect our language preferences? e.g. Show 沙耶 instead of Saya if I prefer non-romanized Japanese, and show Xiao Yi instead of 小伊 if I prefer romanized Chinese. It should be possible to get the language info from the original language of VNs a character is linked to. Ideally speaking, no character should be linked to VNs with different original languages, a new instance should be used for that, so I think this approach would work. (Or we could have language fields for character names as well, like AniDB does) |
| #1485 by Yorhel 2023-02-19 at 17:33 | < report >Yeah I'm still undecided whether to go with your idea or to add per-language character names in much the same way we now handle VNs & releases. The latter is obviously more complete, but also a ton of work and perhaps not worth it given that most localizations don't really change character names anyway. Staff names I'll try to update next, those can be done in the same way as producers. |
| #1486 by Yorhel 2023-02-21 at 13:04 | < report > perhaps I can separate the highlighting option from the [tag + trait] spoiler overrides. Done, with support for custom colors too. |
| #1487 by mikiru 2023-02-21 at 19:07 | < report >Question. Why did all title VN become fully displayed? They used to be smaller, longest titles didn't take up as much space in list or page. |
| #1488 by Yorhel 2023-02-22 at 07:08 | < report >I was planning to move the title truncation from the back-end to CSS, but only updated the back-end and didn't change the CSS yet, heh. Do you have examples where the displayed title is too long? I'll try and do the CSS magic then. |
| #1489 by mikiru 2023-02-22 at 16:20 | < report >#1488 link |
| #1490 by rampaa 2023-02-25 at 17:12 | < report >Can the upper limit of "Display preferences->Language" be relaxed? 5 isn't nearly enough for my use case, i.e.: #1 Language 1, Only if original title #2 Language 2, Only if original title #3 Language 3, Only if original title #4 Language 1, Only if official title #5 Language 2, Only if official title #6 Language 3, Only if official title #7 Language 1, Include non-official titles #8 Language 2, Include non-official titles #9 Language 3, Include non-official titles #10 Original language, romanized |
| #1491 by Yorhel 2023-02-25 at 17:16 | < report >No, 5 is already painful enough. |
| #1492 by marvn 2023-03-09 at 05:23 | < report >I would like to suggest an easily accessible nukige/high sexual content filter button in tag/VN page searches. I think it'd be a huge quality of life improvement to be able to filter them out in one click instead of having to add a tag filter, then invert it and type in the two tags. Would be a lot more approachable for a lot of people as well who might not even know you can invert tags. |
| #1493 by Draconyan 2023-03-09 at 06:00 | < report >@1492: if you select/exclude High Sexual Content, and leave "child tags" selected, then Nukige is also automatically selected/excluded. |
| #1494 by Yorhel 2023-03-09 at 06:48 | < report >A question: Given that VN and release titles now have their original title + romanized title fields swapped in the edit forms, there's now an inconsistency with other database entries that still have the "main (romanized) name" and "original name" fields (i.e. producers, staff & characters). Should I swap the input fields for those entries as well so that everything is "name in original script" + "name in latin script (if applicable)"? |
| #1495 by rampaa 2023-03-09 at 14:25 | < report > Should I swap the input fields for those entries as well Yes.A semi-relevant question: One can currently create a VN entry without providing its romanization (link), is this intentionally allowed? |
| #1496 by Yorhel 2023-03-09 at 15:09 | < report >Alrighty, language preferences also apply to characters now. One can currently create a VN entry without providing its romanization (link), is this intentionally allowed? Kind-of. The script detection isn't all that great and may incorrectly flag a title as requiring a romanization. Not sure how many entries are affected, I should look into that sometime. |
| #1497 by rampaa 2023-03-09 at 15:45 | < report > language preferences also apply to characters now Great! It doesn't seem to affect character pages though (like Saya).Last modified on 2023-03-09 at 15:51 |
| #1498 by Yorhel 2023-03-09 at 16:07 | < report >It did... but in a broken way. |
| #1499 by Marc402 2023-03-09 at 16:15 | < report >The original Japanese name is no longer showing up for me. Only the romanized one is visible. |
| #1500 by Yorhel 2023-03-09 at 16:19 | < report >You've got "Original language" set to romanized in both title and alternative title in your profile, so yeah, working as intended. |