| Summary | selecting tags with umlaut causes a page not find 404 |
| Queue | Ansel |
| Queue Version | 1.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | michael (at) bigmichi1 (dot) de |
| Created | 01/07/2010 (5655 days ago) |
| Due | |
| Updated | 02/23/2010 (5608 days ago) |
| Assigned | 01/07/2010 (5655 days ago) |
| Resolved | 02/11/2010 (5620 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
latin1_german1_ci and also the varchar field to latin1_german1_ci for
tags, i tell horde to use latin1 as charset, but still i cant use url
rewriting only get based urls work
State ⇒ Not A Bug
that it is using.
if i add a new tag with a umlaut i got the same be behavior
Is your DB actually using UTF-8?
Are these new tag entries, or were they existing from an earlier
version? In other words, if you add a new tag, do you still get the
same behavior?
New Attachment: db-screen.JPG
New Attachment: horde.sql
$conf['sql']['protocol'] = 'unix';
$conf['sql']['database'] = 'horde';
$conf['sql']['charset'] = 'utf-8';
$conf['sql']['splitread'] = false;
$conf['sql']['ssl'] = false;
$conf['sql']['phptype'] = 'mysqli';
attached is the current schema of the horde database
State ⇒ Feedback
Priority ⇒ 1. Low
and what is you setting of $conf[sql][charset]?
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Ansel
Summary ⇒ selecting tags with umlaut causes a page not find 404
Type ⇒ Bug
Priority ⇒ 2. Medium
the tag in the tag cloud i got the following 404 from my webserver
'The requested URL /ansel/tag/rügen/ was not found on this server.'