Age | Commit message (Collapse) | Author | Files | Lines |
|
This will correctly handle fetching stuff from the database when
permanent filters are enabled.
This update also removes compatibility with some old VN browse URLs. The
old 'ti' and 'te' (tag include/exclude) query parameters are now
ignored, and searching for a language in the query string (e.g.
"q=English") won't enable the language filter.
|
|
|
|
This can be seen as a partial revert of
0a4f97f0186d6941a4cab2e3bd05201f1fed1441.
I used to think using NULL for special values is more "correct" in
database terms. But in the end I guess I should be aiming for whatever
solution is easier. Both are "correct" in a sense anyway.
|
|
Had to fix some bugs here and there and add some new functionality to
the abstractions at some places, but it appears to be working now. There
are still a few TODOs left, I'll get to those in a bit.
|
|
fil_parse() now checks for proper formatting of the string and ignores
key/value pairs that are not the list of allowed keys. This makes it
impossible to provide extra, unintended, arguments to dbReleaseGet(),
such as 'results'.
|
|
It seems a comma has to be escaped in query string values. A ~ doesn't
and thus makes the URIs significantly shorter.
|
|
There's no validation of the filter string yet, and somehow I don't feel
like adding that; it's a lot of code and there's nothing to protect -
the values are inserted using parameters into a SELECT query, the worst
thing that could happen is the user receiving a 500.
Also, I've started using the perl '//=' operator, which was added in
5.10. This removes support for older perls.
|
|
This adds a new column to the vn table: c_search, which holds the
normalized titles for speedy search results using LIKE.
Also split some functions from VNDB::Func that didn't require YAWF into
a VNDBUtil module, so Multi can also make use of them. The normalization
functions are the same for Multi and VNDB, after all.
The API and Multi::IRC still use the old search, these should be updated
as well.
|
|
|
|
The previous version also had a problem with closing tags when a
$maxlength was defined. With $maxlength, not all tags actually open a
tag in HTML, after all.
|
|
Should be converted to enums at some point... integers don't do the
trick here.
|
|
and age()
|
|
You can ignore the entries in lang.txt, those are simply for testing
purposes.
|
|
|
|
<RT> yorhel, in the browse view, can you put the date in italics when
the first complete release date is not "fully qualified" ? e.g. 2008-08
|
|
Conflicts:
lib/VNDB/DB/Discussions.pm
util/updates/update_2.3.sql
|
|
|
|
...I could've also just used a gradient background image, which is
easier to do and looks better... but I hate solutions that require
external resources. >.>
|
|
VNDB::Func::bb2html()
|
|
|
|
|
|
|
|
|
|
|
|
Three-box-layout didn't work very well together with the screenshots
on the homepage and the CSS icon hack needed a to get rid of
a strange top margin.
With this, the following browsers should render all pages correctly:
FF2, FF3 and the latest Opera, Safari and Chrome
|
|
These changes are all pretty much related, so couldn't really do
that in multiple commits.
|
|
|
|
DB/{Votes,VNList,WishList}.pm into ULists.pm
|
|
|
|
|
|
Well, 'proper'... I should fix the handling of deleted users in
the database, as the current solution is far from perfect.
|
|
Character-level diffs instead of the old word-level diffs.
Still only works on plaintext, though.
Not really sure about the style, either.
|
|
The general concept and method is really the same, this version just
does a few things different to ensure correct parsing and HTML output.
|
|
The bb2html() function was written by 3dB a while back (as a replacement
for the 1.x summary() in defs.pl). The function wasn't quite finished
and still had a few small problems if I recall correctly, but I kind of
forgot what did and what didn't work, so I just copied 3dB's code without
modifications.
Anyway, the producer page is now pretty much finished!
|
|
|
|
CommonHTML in LayoutHTML, and abstracted the browser generation
I was planning to commit often, but I still end up doing everything
in one commit >.>
|