Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This fixes two things:
- It's not possible to create two accounts with the same mail address
with different case (although the user+xyz@domain trick still works).
- The password reset form is now case-insensitive as well. Some people
had problems with the case-sensitive behavior in the past.
|
|
|
|
|
|
Compresses a little better. I reduced the number of iterations required
to find the optimal image size in spritegen.pl, but generating the
icons.png is *incredibly slow* when combining zopflipng with the 'slow'
option. It's possible to parallelize the calculation and use multiple
cores to speed it up, but that seems overkill.
Some icons.png compression stats:
METHOD SIZE RUNTIME
default 18103 <1sec
slow 17941 few secs
pngcrush 15385 <1sec
pngcrush+slow 15148 few mins
zopflipng 14986 few secs
zopflipng+slow 14898 ~1 hour
|
|
The API IP address doesn't change often, but we don't want months of
downtime when it does.
|
|
Newer versions of DBD::Pg do this automatically.
|
|
https://vndb.org/t2520.185
|
|
Apparently IE doesn't like it when you put a HTMLCollection object
inside a DOM value.
|
|
Fixes https://vndb.org/t950.210
|
|
|
|
|
|
|
|
|
|
The comment already suggested this:
I wonder whether it's better to just ask database for character list
instead of doing this manual group/sort
So yeah, let's just do that.
|
|
|
|
|
|
|
|
The styling of the staff info can be a bit awkward at times, but it
looks slightly better than a table, IMO. I didn't really know what to do
with the the seiyuu info - it wastes a lot of screen space in its
current implementation, but I can't think of anything better at the
moment.
|
|
|
|
|
|
|
|
- Merged polls table into threads table. Not much of a
storage/performance difference, and it's a bit simpler this way.
- Merged DB::Polls into DB::Discussions. Mainly because of the above
change in DB structure.
- Add option to remove an existing poll.
- Allow preview and recast to be changed without deleting the votes
- Set preview option by default. Because personal preferences. :)
- Minor form validation differences
|
|
|
|
|
|
|
|
Having the time display is quite useful. It does make the listings look
more cluttered, but meh.
|
|
|
|
|
|
|
|
|
|
|
|
While helpful, it's also rather dominant. We're not that desperate for
new contributes anymore.
|
|
Instead of the JS hack.
|
|
https://vndb.org/t950.103
|
|
The possible values of the rel attribute is fixed, it's not supposed to
be a free-form field.
|
|
I'd have preferred to stick with XHTML 1.0, but unfortunately browsers
won't allow you to use modern Javascript APIs with an older doctype.
Note that most pages don't actually validate correctly as HTML5, I'm
relying on browsers to be lenient.
In either case, I'd like VNDB to stay valid XML (XHTML5, then), and
luckily that shouldn't be a problem.
|
|
DBD::Pg doesn't recognize the 'xml' data type as textual data, and thus
doesn't decode it for us. This fixes the display of non-ASCII
characters.
|
|
They had to be deleted from the database at some point, otherwise we
still have thousands of easily-cracked password hashes in the database.
Note that I could have opted to use scrypt on top of the sha256 hashes
so the passwords would remain secure without needing to reset
everything, but doing that after one year of switching to scrypt is
likely not worth it. Everyone who still actively uses his account has
already been converted to scrypt, everyone else should just reset their
password whevener they decide to come back.
|
|
|
|
|
|
|
|
|
|
|
|
'<> ANY' doesn't work that way. NOT EXISTS() is also pretty fast and
does what we want.
|
|
Turns out the anime data hasn't been updated in a few months. Oops.
|
|
Broken in bbe989de364ddc654bfc6385e22f1eaff23faad1. I forgot that floats
can't accurately represent some .5 numbers.
|
|
I don't know why I didn't apply this one before, I did make this change
when benchmarking the fulltext search queries and with the introduction
of the bb_tsvector() function this change pretty much always improves
performance.
|
|
The new database schema doesn't allow an alias to be removed when it is
still linked to a VN.
|
|
This broken filter would cause all staff info to be deleted from a VN
upon edit. Not so nice.
|