Age | Commit message (Collapse) | Author | Files | Lines |
|
Haven't found any bugs this way, yet. I doubt there'll be any problems,
but it's a nice new feature that could help quite a bit. :-D
|
|
Configuration change: Make sure you more the cookie_prefix option from
%S to %O. (It's now a TUWF option rather than a VNDB one)
|
|
There may still be some bugs present and I've only converted the points
where TUWF is incompatible with YAWF. The new TUWF features are not in
use yet, I'll do that later on.
Note that, in order to run the new code, TUWF must be installed on your
system. The configuration for the TransAdmin plugin has also changed.
Other than that there shouldn't be any issues.
|
|
This finalizes the moderation tag vote overrule. And Damnit, the logic
behind saving the tags to the database isn't fun, I hope I haven't made
any mistakes there.
|
|
This is the second step in adding support for overruling tag votes by
moderators.
This required a different approach to calculating the score in
dbTagStats(). For some reason this approach turns out to be slightly
faster as well...
|
|
This finalizes the permanent filters feature.
|
|
Performance. Those featues are hardly used, but they can block other
visitors when used in bad combinations.
|
|
This makes the UI slightly uglier and less intuitive. I'll see if I can
find a way around that. This update is required for the permanent
browsing filters to be fast and reliable.
|
|
It's mostly a moderation thing, shouldn't get indexed.
|
|
That should be all relevant pages, I guess.
|
|
|
|
The new tag link browser has replaced the crappy old user-tags-browser.
|
|
Still need to add some links to the browser to parts of the site.
|
|
|
|
This replaces the "cookie_auth" setting, and applies to all cookies in
use by VNDB.
|
|
|
|
|
|
The current error message isn't really intuitive, though...
|
|
It should work perfectly now...
|
|
|
|
Minor bug introduced in e69b417f
|
|
The return value of dbTagTree() is also somewhat easier to work with.
|
|
The ORDER BY was previously specified using an 'order' argument, which
would then be directly inserted into the query. The new method is the
same as what I used for the public API: two 'sort' and 'reverse'
arguments. This should be less error-prone and more readable.
This changes quite a lot of code, so I hope I haven't forgotten to
update something along the way.
|
|
With this method I managed to reuse the VN list table code for the lists
on both the VN browser and the tag pages. And optimized away the
dbTagVNs() function while I was at it (dbVNGet() is powerful enough)
|
|
For three reasons:
- Speed
tag_vn_calc() is now more than 10 times faster (granted, it could
have been a lot faster even with the bayesian rating, but whatever)
- Consistency with the tag scores displayed on the VN pages (which are
raw averages as well)
- It didn't always make sense
|
|
Forgot that c_popularity was used there as well.
|
|
|
|
|
|
+ removed last traces of forms.js
+ converted code to use tables, as that is easier to expand more
accurate for this purpose. The reason I probably didn't use tables
before was that the innerHTML property doesn't work on tr elements.
The split was mainly because the producer linking is going to be
expanded with an additional field later on.
|
|
- You can now click the spoiler column to scroll through the options
- Or mouse-over the spoiler column to see a JS dropdown with the options
(no more select box, which introduces several more clicks to do the same)
|
|
|
|
Interface consistency.
|
|
|
|
|
|
The subform id is now passed to htmlForm() as first formpart item. This
way the id won't change even if the title does, which will be the case
with the interface translation.
|
|
and age()
|
|
|
|
User ranks are easy... but the language names are used everywhere!
|
|
|
|
It's still not perfect, though:
- New version is table-based - meh.
- Uses negative margins more than once - meh!
- Only works if any of the columns has enough content to wrap. If all
content fits in the columns without wrapping, the total table width
falls back to the "min-width: 100%" statement - which, with the
negative margins, isn't really 100%. MEH!
Still... it looks better than the previous solution.
So far tested on FF3.5, Opera 9.something, and some semi-recent version
of webkit. Reported to work fine on IE7 as well.
|
|
Ideally, that shouldn't be necessary, but I can't think of a way to keep
the tags_vn_bayesian table up-to-date without a huge performance
penalty.
|
|
Everything has now finally been converted to use the PgSQL LISTEN/NOTIFY
feature. This commit removes the last Tie::ShareLite dependency.
|
|
|
|
This should make a nice connection between the few kinds of database
entries we have.
|
|
|
|
|
|
|
|
|
|
|
|
If they can view them, hiding the tags doesn't really make much sense.
|