Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Now it's finally possible to run multiple VNDB's with different
databases on the same domain without constantly getting logged out.
|
|
I could swear the user pages have always been noindex'ed... hmm.
|
|
|
|
|
|
This required a new 'split' option to consider a string as an array.
|
|
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.
|
|
|
|
Crawlers would often find such pages, and the query would often take
more than a second to finish, in some extreme cases even 10 seconds.
This fix converts an intermediate result into an array, forcing the
query planner to evaluate the subquery first, resulting in a far more
optimal query plan.
|
|
|
|
substr outside of string at /www/vndb/lib/POE/Filter/VNDBAPI.pm line 124.
I have no idea what input caused JSON::XS to return an invalid character
offset... but oh well.
|
|
|
|
|
|
1. Don't try to normalize the GTIN code in the releases form when it's 0
2. Don't try to gtintype() *every* number in the search
|
|
We have to assume that the input doesn't always have enough zeros,
to fill the 12 characters, otherwise UPC codes fail when they are
fetched from the database (which is stored as a bigint, no zero padding
in the output). Instead, we'll just add the zeros ourselves up to 12 for
normalization purposes.
|
|
You can't quite check the length of the GTIN code if you strip away
zeros in the beginning, right?
|
|
|
|
|
|
|
|
|
|
|
|
The layout looks better without that.
|
|
...rather useless option to have.
|
|
So that the count displayed in the main menu is updated immediately,
rather than on a subsequent pageview.
|
|
I may do the docs later as well, when I'm terribly bored again.
|
|
Conflicts:
data/lang.txt
|
|
This one is also configurable, but mainly because I want to avoid
generating several thousands of notifications for a single action...
|
|
And added a settings window where you can disable this notification,
which is something you really want to do if you're an active
contributor...
|
|
And changed vn.c_languages to an array type while I was at it. This
required some changes in the Perl code, and I found a bug in DBD::Pg
while I was at it:
https://rt.cpan.org/Ticket/Display.html?id=54224
Luckily, there's an easy workaround for that.
|
|
|
|
|
|
Complex queries...
|
|
These aren't likely to change anyway, and things will become less easy
to display when other types of notifications are added.
|
|
More intuitive to allow clicking on that as well to open the
notification.
|
|
|
|
|
|
Too many "HEY CAN YOU RECOMMEND ME .." people going around. The channel
is crowded enough now.
|
|
|
|
An expiration date doesn't make much sense if it's both not used and if
it can't be configured by the user, so just make this a timestamp to
indicate when the session has been added, which, while still not really
used, is more valuable.
|
|
If we're going to automatically remove older sessions, it would make
more sense to remove unused sessions, rather than old sessions that are
still in use. But we first need to keep track of when a session has last
been used to do so...
|
|
Setting the l10n cookie is now done from a separate url: /setlang
This makes the language determination code less complex, and makes sure
nobody links to pages that change the UI language without intending to.
(I've seen some links floating around with the l10n parameter included,
which is... bad)
|
|
The current setup should be able to handle all kinds of notifications,
though only PMs are implemented at this point. More to come.
|
|
The current error message isn't really intuitive, though...
|
|
Added a userid field in the skin config files, from which the credits
are loaded. Now I don't have to constantly update d7 for every language
when something changes in the skin files.
|
|
And updated skingen.pl and vndb.pl to make use of this abstraction.
|
|
This way you can easily see the difference between an announcement and a
regular user-requested reply.
|
|
They used to be hidden from all edit histories, but there's not really a
point in hiding them. In fact, it'll only confuse people who just got
their DB entry deleted and can't find any evidence that it even existed
at all.
|
|
This is implemented by adding ihid (item hidden) and ilock (item
locked) columns to the changes table,
The (vn|release|producer).(hidden|locked) columns now work as a
cache, refering to the changes.(ihid|ilock) columns with
changes.id = (vn|release|producer).latest.
The cached columns are updated automatically each time a new revision is
inserted.
This is a pretty large change, bugs are quite likely.
|
|
|
|
|