Jump to content

Jan P.

  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Hamburg, Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jan P.'s Achievements


Newbie (2/6)



  1. Dear ProcessWire community, I recently found an issue with unicode characters used in CKEditor / Input fields. Most likely it seems to be a CKEditor configuration issue. Maybe someone has a hint to solve this. First of all my setup: ProcessWire 3.0.184 (latest master release) running on PHP 7.4.28 Input field Textarea / CKEditor with Markup HTML / use ACF (yes / no – doesn’t matter) / use HTML Purifier no When I put a random Chinese character into this field (decimal 27721) so Ampersand Sharp 27721 Semicolon – it works perfectly out of box. This unicode character will be displayed and rendered. Now my problem: When I put one of those new fancy smiley unicode characters into this field (decimal 128513) the whole source code breaks after this point but only after pressing the save button. It is totally weird behaviour. The significant difference is the high decimal number. I tried a few configuration suggestions from the CKEditor Reference Page for example: config.entities = true config.entities_processNumerical = true config.entities_additional and exactly allowing decimal numbers Nothing works. Does anybody have a good idea or is it a known CKEditor bug?
  2. Hello, no, there is no need to change the vendor .htaccess file to do this. At first sight I also thought it would be necessary but it is not.
  3. Hello, we found the following solution that is quite similar to the suggestion from Autofahrn. Our setup includes two languages - de (german) as default for *.de domain (default language) - en (english) for *.com domain In _init.php there is just: if (preg_match("/(:2284|\.com)/", $config->httpHost)) { $user->language = $languages->get('englisch'); } Your question no. 2: It is important that you configure the settings for your root page to "/" for each language. In that case PW doesn't prefix your URL paths for the children. Be careful! In case you use the front page editor - when a child page has the same path for every language, the front page editor is not able to save the page correctly. You have to use the backend. But if there are differences, for example *.com/imprint and *.de/impressum - the front page editor works fine.
  • Create New...