Age | Commit message (Collapse) | Author | Files | Lines |
|
filFetchDB() is not used for the release filter on the VN browsing
interface, so I've moved the compatibility stuff into a separate
filCompat() method that can be called from Handler::VNBrowse.
|
|
Been wanting to do this for a long time - using an integer index into an
array that changes once in a while is way too fragile. Doubly so when
said indices are also used in filters and URLs that can't be updated
every time a new resolution is added.
|
|
https://vndb.org/t950.512
|
|
https://vndb.org/t11296.3
(And I forgot to add update_20180929.sql in the previous commit)
|
|
https://vndb.org/t11296
|
|
https://vndb.org/t950.481
Also, the resolution should really be stored as an ENUM in the database,
this integer thing is waay too fragile.
|
|
This also handles the uppercase İ, as that is already converted to
lowercase ı in an earlier step.
|
|
https://vndb.org/t2520.265 - 270.
|
|
https://vndb.org/t950.456
|
|
|
|
I'm sure this breaks styling of a few things, I'll adjust those as I
find them.
|
|
Icon created by fuukanou: https://vndb.org/t10665.49
File size reduced a bit further by removing metadata and using scour
Closes #3
|
|
|
|
|
|
As discussed in https://vndb.org/t10665
|
|
|
|
https://vndb.org/t950.432
|
|
https://vndb.org/t2520.259
|
|
https://vndb.org/t3599.201
|
|
If you don't really care about the data in your Docker's Postgres DB,
then you can just update with:
docker volume rm vndb-data
docker volume create --name vndb-data
docker build --pull --no-cache -t vndb .
If you do want to keep your data, the process is roughly as follows:
- Do a pg_dumpall from your current docker image to save the data.
- Run the above commands to upgrade
- Import the database in the new docker image
(cherry picked from commit c278eec720b78624580f844d8289ddb575035138)
|
|
https://vndb.org/t10472
|
|
There's still a glitch that, when a character is linked to a deleted
release, the release selection will not show up in the form. But that's
much easier to work around.
|
|
https://vndb.org/t950.416
|
|
output
|
|
Fixes https://vndb.org/t2520.250
|
|
|
|
|
|
https://vndb.org/t950.410
|
|
This touches a bunch of things:
- Adds a new first-class database entry type
- Removes the d+.+.+ BBCode link syntax, adds a new d+#+ and d+#+.+
link syntax (references have been updated where possible)
- Adds a new dependency on Text::MultiMarkdown
|
|
For consistency with the VN & character alias fields. It's also less
ambiguous, as there are a few aliases that contain commas.
|
|
Otherwise the vndb_site/_multi users won't have usage rights on those.
Fixes https://vndb.org/t10218.6
|
|
+ a bit of tooling to make it work.
The database was contributed by tigershark, with a few minor additions
by me.
|
|
|
|
Should fix https://vndb.org/t2520.237
|
|
inmediate container <abbr>.
|
|
Should fix https://vndb.org/t9425.11
|
|
https://vndb.org/t2520.233
The old bb2html() blindly replaced [url=..] anywhere inside the matched
token, and did not require that the [url=..] was itself the token. I've
made the tag matching more strict to make sure that [something[url=..]
is now properly tokenized.
This also affects other tags, so it's likely that there's some input
that the old bb2html() would still have handled differently.
|
|
|
|
https://vndb.org/t9992.21
|
|
https://vndb.org/t9992.16
|
|
|
|
|
|
|
|
This is based on the API that I described in https://vndb.org/t5564.12
It's mostly bug-compatible with the old bb2html(), main differences:
- <br /> -> <br> for no reason
- Doesn't sporadically add a wrong </div>
- $rmwhitespace now also after [/code]
Most of the test cases were contributed by flan <flan@flande.re>
|
|
This was already the case in the original patch, I broke it with the
code style changes.
|
|
|
|
|
|
These are just style consistency changes, functionally equivalent.
|
|
It's been a while since I had static/f/ in git, so I had to adjust
.gitignore a bit.
The CSS changes are purely opinion, but it does integrate better with
the existing layout.
Everything else are bug fixes.
|
|
|