Hello.
I've successfully installed Mantis 1.0.8. with PostgreSQL 8.1 but I'm running in trouble each time I try to add a new user name (or a project) with spanish acents (let us say, "Andrés"...)
When adding a such user I get that "invalid byte sequence for encoding UTF8" error, and adding a project with acents I get a data base query error.
PostgreSQL is set to UTF-8 (actually, all my other databases run fine with such a setup). The problem seems related to page encoding, because configuring my Firefox browser to UTF-8, I'm able to add that user but, of course, then all accented spanish words look with plenty of ? because Mantis pages are served as iso-8859-15.
Any help? (BTW: Manual pages are inavailable just now, so I'm unable to look there for some help)
Regards,
NK.
Problem adding users and projects names with accents (UTF-8)
Moderators: Developer, Contributor
Upgrade to Mantis 1.1.0a4.
Want more plugins to customize Mantis?
=> http://deboutv.free.fr/mantis/
Mantis: 1.1.0, 1.1.0a2
PHP: 5.0.4
SQL: MySQL 5.0.19
OS: Linux
=> http://deboutv.free.fr/mantis/
Mantis: 1.1.0, 1.1.0a2
PHP: 5.0.4
SQL: MySQL 5.0.19
OS: Linux
Done. Actually, I did a fully new reinstall, but now I get another problem during the database creation, precisely in the Create Schema ( CreateTableSQL on mantis_bug_table) step:deboutv wrote:Upgrade to Mantis 1.1.0a4.
ERROR: «sticky» column is boolean type but default expression is of type integer
Details of the error:
BAD CREATE TABLE mantis_bug_table ( id SERIAL, project_id INTEGER DEFAULT 0 NOT NULL, reporter_id INTEGER DEFAULT 0 NOT NULL, handler_id INTEGER DEFAULT 0 NOT NULL, duplicate_id INTEGER DEFAULT 0 NOT NULL, priority INT2 DEFAULT 30 NOT NULL, severity INT2 DEFAULT 50 NOT NULL, reproducibility INT2 DEFAULT 10 NOT NULL, status INT2 DEFAULT 10 NOT NULL, resolution INT2 DEFAULT 10 NOT NULL, projection INT2 DEFAULT 10 NOT NULL, category VARCHAR(64) DEFAULT '' NOT NULL, date_submitted TIMESTAMP DEFAULT '1970-01-01 00:00:01' NOT NULL, last_updated TIMESTAMP DEFAULT '1970-01-01 00:00:01' NOT NULL, eta INT2 DEFAULT 10 NOT NULL, bug_text_id INTEGER DEFAULT 0 NOT NULL, os VARCHAR(32) DEFAULT '' NOT NULL, os_build VARCHAR(32) DEFAULT '' NOT NULL, platform VARCHAR(32) DEFAULT '' NOT NULL, version VARCHAR(64) DEFAULT '' NOT NULL, fixed_in_version VARCHAR(64) DEFAULT '' NOT NULL, build VARCHAR(32) DEFAULT '' NOT NULL, profile_id INTEGER DEFAULT 0 NOT NULL, view_state INT2 DEFAULT 10 NOT NULL, summary VARCHAR(128) DEFAULT '' NOT NULL, sponsorship_total INTEGER DEFAULT 0 NOT NULL, sticky BOOLEAN DEFAULT 0 NOT NULL, PRIMARY KEY (id) )
I'm using PostgreSQL 8.1 but this problem didn't occur during my previous Mantis 1.0.8 installation. Should be installing 1.0.8 again and upgrading the Mantis application only to 1.1a4 a better (and secure) way to do?
Best regards,
NK.