Age | Commit message (Collapse) | Author | Files | Lines |
|
This takes less code and may (or may not) be more efficient since it
does not require any HDD I/O while performing some checks.
|
|
Cleaner this way.
Also found two occurences of manually HTML-escaping text for textareas,
which isn't necessary anymore.
|
|
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
|
|
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.
|
|
The check is quite basic and you can easily get around it. It's just
intended to warn about common mistakes.
|
|
The official flag of untouched relations wasn't properly copied from the
old revision.
|
|
This is a very old bug. Never fixed it before because I couldn't think
of a clean/easy solution and it wasn't important to waste my time on.
|
|
This is the first part. The flag is stored in the database, can be
edited through the usual VN edit form, and is displayed in the diff
viewer.
Things to do to make this feature fully functional:
- display "official" status on VN page at the relation listing
- update relation graphs to display unofficial relations differently
- update guidelines
|
|
|
|
And clean up the alias field before it gets inserted into the DB.
Does not provide any feedback to the user, let's just hope our users are
clever enough to figure out what happened.
|
|
|
|
|
|
The layout looks better without that.
|
|
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.
|
|
This will make it easier to do automated edits, either from cron jobs,
Multi, update scripts, or from within SQL triggers.
So far only the VN related functions have been defined/updated, trying
to edit/add releases or producers will not work at the moment.
The functions for editing or adding a new database entry have been
merged, as the procedure is rather similar.
util/dump.sql will be updated later on.
|
|
Some browser compatibility stuff and some stupid bugs.
|
|
This column was used to differentiate between automated edits and user
edits, but that later changed to checking for changes.requester = 1.
The column has since never really been used, and due to a bug introduced
in VNDB 2.0, it has never been updated, either. Meaning it's not even
accurate for any database changes made after december 2008...
|
|
And also changed the way the item_table.latest column was updated: it is
now only updated after the revision insert has completed, making it
easier to write trigger functions in SQL.
|
|
|
|
|
|
+ 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.
|
|
+ Some fixes and improvements in the dropdown search
+ Renamed 'relations' field to 'vnrelations', as other relations are
going to be implemented as well
New relation editor code is somewhat smaller than the old, mostly thanks
to the tag() function. Also tried to make things less error-prone and
easier to maintain by referencing things using self-explainable class
names instead of the ordering of the HTML tags.
|
|
OK, these are actually two separate things: to make the relations
translatable they didn't necessarily have to be stored as enum, and I
could've also converted them to enum but not have it translatable.
Nevertheless, it was easier to just do both at the same time.
Also note how I used the string "$____vnrel_<rel>____$" as identifier in
the relation graphs while I could have used something a lot shorter
("$<rel>$" would have been fine, for example). This is done so that
graphviz can make some space for those relations - the long identifier
gives a slightly more realistic representation of the actual length of
the relation titles.
|
|
|
|
As they would soon be dead links, anyway.
|
|
|
|
|
|
|
|
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.
|
|
This finishes Util::CommonHTML, with the exception of htmlVoteStats
|
|
|
|
|
|
Everything has now finally been converted to use the PgSQL LISTEN/NOTIFY
feature. This commit removes the last Tie::ShareLite dependency.
|
|
This finished the rewrite of Multi::Image and everything surrounding it.
|
|
Yay! Another weird shared-memory-command optimized away. And the image
resizer reacts a lot faster now. Noticably, even.
|
|
The notify is called from a trigger function, which is called on any
UPDATE or INSERT INTO query of which the lastfetch column is NULL.
This guarantees that anime info in the DB will always be updated, no
matter how its inserted.
|
|
|
|
|
|
The categories are still available for viewing and editing to aid
in the transition to the tagging system, but editing has been removed.
|
|
|
|
DB/{Votes,VNList,WishList}.pm into ULists.pm
|
|
Including anything related to editing, item histories, etc.
No need to have those pages in google, is there?
|
|
|
|
Interface and code are mostly the same as the 1.x version, but with
some tiny improvements.
|
|
...but not yet uploaded, and we'll need a more userfriendly interface
|
|
|
|
|
|
The dropdown search (ds* functions) is pretty generic, and could be
used for other things as well.
|
|
By specifying an ID, we still need a JS-powered search >.>
|
|
Viewing, changing and deleting relations already works, adding not yet.
|