tigefa4u projects Trac

TicketClone sample plugin should use a POST in order to be able to clone tickets containing a big description.

This reverts r6322 but adds a ''preview'' parameter, which is another way to avoid the problem originally addressed in that changeset.

Closes #7839.

MultiRepos: fix Repository Index so that it can be sorted by date even in the presence of repository entries having errors.

Update Japanese translations.

Submitted by: IWAI Masaharu (and the Shibuya Trac members)

Search could trigger an !AssertionError if the term consisted of whitespaces only.

MultiRepos: merged [8082] from 0.12dev

0.12dev: ported r8078 and r8080 from 0.11-stable

MultiRepos: Merged [8079] from trunk.

'''For people who have already upgraded their database to version 22 or 23, this requires manual intervention on the database.'''

You have to remove the `cache` table and re-create it by hand:
{{{
DROP TABLE cache;
CREATE TABLE cache ( id text PRIMARY KEY, generation int );
}}}
(for SQLite; or the equivalent for your database)

See #8197.

Fix some long standing issues in the WSGI layer:
- stop handling a request early when the client disconnected (fix #3043)
- don't write to the client if the file descriptor is already closed (fix #1183)

0.12dev: Renamed the `key` column of the `cache` table to `id` for MySQL compatibility, and changed the type of the `generation` column to `int`.

'''For people who have already upgraded their database to version 22, this requires manual intervention on the database.'''

You can either remove the `cache` table and re-create it by hand:
{{{
DROP TABLE cache;
CREATE TABLE cache ( id text PRIMARY KEY, generation int );
}}}
(for SQLite; or the equivalent for your database)

Or you can downgrade the database version, drop the `cache` table, and upgrade again:
{{{
UPDATE system SET value=21 WHERE name='database_version';
DROP TABLE cache;

trac-admin $TRAC_ENV upgrade
}}}

Closes #8197.

!InterWikiMap component was not always registered in change_listeners.

On trunk, this prevented the proper update of the cache. Fixing on 0.11-stable as well, as the component registration issue is certainly the same there.