| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
elm.min.js.gz shrunk by 9919 bytes. user.min.js.gz is now 9681 bytes.
Not a totally fair comparison and those few bytes are completely
irrelevant, but it at least shows that I'm not making things more bloated.
|
|
|
|
Previous solution relied on negative margins more than I liked. This
solution is still surprisingly fiddly.
This requires TUWF commit 4b0e2df89fe180bfa2f3da195a80684a46a649db
|
|
Hopefully without breaking anything.
Switched to using flexbox for the homepage boxes instead of grid, in
order to fix an overflow issue on Pale Moon. But I later fixed a similar
issue with the relation graphs and history tables, so perhaps that
switch wasn't necessary.
|
|
|
|
To reserve <b> for the standout styling.
|
|
Which is also kind of an abuse, but at least the semantics are much
closer.
(Next up: the standout class. Slowly working towards a "font: inherit"
and "color: inherit" reset, which'll remove the need for a bunch of ugly
workarounds)
|
|
|
|
support
|
|
This is in preparation for getting rid of the CREATE TEMPORARY VIEW
commands in order to switch title preferences:
https://dev.yorhel.nl/doc/vndbtitles
The JSON storage approach ended up being quite as mess, too.
Also "fixed" it so that selecting Chinese will automatically also select
the scripts, if there's enough slots.
|
|
|
|
|
|
Currently has 851 million password hashes, taking about 8G of space with
the current approach. It's simple and fast, so should be worth it.
inb4 complains about "why can't I use my password anymore!?"
|
|
+ update filters and APIs to respect the 'listread' permission.
|
|
|
|
|
|
|
|
|
|
As discussed in https://vndb.org/t13027 and from
https://vndb.org/t6138.327 onwards.
|
|
Problems with the old implementation were that the setting wasn't an
intentional user action, so there were a LOT of preference writes that
were reverted a minute or so later. Wasting both server and visitor
time. For regular visitors, the localstorage-based approach also caused
a reflow if their preferences didn't match the default.
Downside of the new implementation is that regular visitors can't change
their preference at all anymore, this now requires an account. :/
|
|
For better consistency with other settings. This means it is not
remembered for regular visitors anymore, and there's now an unused
cookie in people's browser that should eventually be deleted.
|
|
|
|
Currently a bit of a regression for users who want to cycle through the
skins, as you'll get directed back to the first tab upon saving. Let's
see if I can improve that.
|
|
|
|
selected multiple times
|
|
+ don't serialize boolean fields when they're false.
|
|
Decided to stick with the generic "Chinese" option for staff and
producers, while forcing a selection of either Simplified or Traditional
for VNs and releases.
This implementation is a bit ugly, the information should be generalized
into VNDB::Types insteasd.
|
|
The old 'Chinese' option should not be available for selection in new
entries, but I'll have to fix that later.
|
|
|
|
|
|
|
|
|
|
There's no way to list or aggregate the votes yet, and I'm not fully
sure the data model is what it should be. Hence testing.
|
|
|
|
|
|
I had wanted to split this up into multiple commits and roll out in
stages, but couldn't really find a natural way to do so. There are
several places that take a generic identifier and expect it to work the
same for all entries they support, so changing one entry at a time
wasn't going to be any easier. Only the tags & traits haven't been
updated yet, I'll convert those later.
While this is a major change and affects a lot of code, the individual
changes are all pretty simple. I'm surprised how much code did not have
to be updated at all. No doubt I've missed a few places, though, so this
commit will almost certainly break something.
|
|
https://vndb.org/t950.830
|
|
The boardmod flag will also determine the review moderation permissions.
|
|
|
|
|
|
|
|
Ugly fix for an ugly issue.
|
|
Same idea as 00fbcdf96432efad85abdbc7392d493409a4c253. Not sure why it
hadn't occurred to me before, seems like such an obvious thing to do.
|
|
dbmods can now change other users' "edit" permission, tagmods "tag",
etc. As I hinted to from be5ee198129301d84912380ed8d1636ad32f68b3
This required the user edit form to be restructured a bit so only people
with the proper permissions get to see the proper form sections.
|
|
|
|
Bug (kind of): deleting a user with !perm_imgvote will suddenly cause
the votes to count again. Need to take care to delete the votes instead
in that case.
|
|
This simplifies several actions and makes permission checks more
obvious. This is also yack shaving for another feature I've been
planning to add: boardmods should be able to set other users' "board"
permission, tagmods for tags, etc. So that partial user bans don't need
the full "usermod" permission.
|
|
endpoint
The new elm_api() function now creates an API endpoint (like json_api())
and generates a corresponding Elm module to interact with that API (like
elm_form()). The API endpoint URL is now derived from the name of the
Elm module, so there's no need to think of a separate URL and less prone
to making typos when using that URL from Elm.
Reduces the boilerplace a bit as well.
|
|
Old VNDB::* code still uses that preference in a few places, that needs
to be fixed.
|
|
|
