Bug #21002
closed
message to reviewer has troubles with umlauts
Added by Georg Ringer about 15 years ago.
Updated almost 11 years ago.
Description
IMO there is a problem with the javascript prompt which is used to send e message to the next step in the "workspace flow", e.g. if an element is rejected or sent to the reviewer/publisher.
if I add an umlaut, no message is getting saved!
(issue imported from #M11886)
Hi Georg,
can you please give a short step by step info how to reproduce and which character set you're using in your backend (UTF-8, ISO8859-1, ...)? Thanks in advance!
how to reproduce:
1) install sysext version, as admin just switch to any workspace, add a new content element
2) switch to the version module and send the content element to the revieer
3) in the js popup, add a dummy text containing an umlaut
4) move the cursor over the stage information and see if the text has been saved
it works fine with the backend set to encoding="iso-8859-1"
=====
if switching to utf8 by using
$TYPO3_CONF_VARS['BE']['forceCharset'] = 'utf-8';
$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'set names utf8;';
+ an additional DROP TABLE `sys_log` and recreation of the table in the install tool and the same thing doesnt work anymore
=====
additional strange thing: i try to switch back to iso-8859-1 (which is also displayed in the header) with a clean table but I can't get the umlauts working right now
- Status changed from Accepted to Closed
- Category set to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
-1)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by