Forums / Install & configuration / Invalid UFT-8 byte sequence detected

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Invalid UFT-8 byte sequence detected

Previous topic

Install & configuration

Next topic

Author	Message
Oliver Pawellek	Sunday 08 January 2006 6:11:46 pm Greetings: I have just attempted to deploy Exponential 3.7.2 with the latest Postgres 8.1 atabase (UTF-8 encoded); most of the initial Exponential setup went somewhat smooth until near the end of installation I receive a database application crash after table for "ezworkflow_process": Excerpt from postgresql log (last three lines): NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "ezworkflow_group_link_pkey" for table "ezworkflow_group_link" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "ezworkflow_process_pkey" for table "ezworkflow_process" ERROR: invalid UTF-8 byte sequence detected near byte 0xf8 I have been informed that Postgres 8.1 is less forgiving about UTF-8 encodings. Has anyone crossed similar problems with Exponential 3.7.2 deployment and the latest Postgres 8.1. Might this be a bug or problem with the php scripts of Exponential 3.7.2? and perhaps has been corrected in the latest SVN stable release.. Oliver Pawellek Saisung Corporation Ltd www.saisung.com
Oliver Pawellek	Monday 09 January 2006 2:04:32 am Please ignore my above recent post. I have just bumped into the Exponential documentation detailing the modification of files site.ini, i18n.ini and template.ini with "Charset=utf-8" within Exponential, and it appears to have cured the utf-8 database encoding dilemma. Oliver Pawellek Saisung Corporation Ltd www.saisung.com

Author

Message

Oliver Pawellek

Sunday 08 January 2006 6:11:46 pm

Greetings:

I have just attempted to deploy Exponential 3.7.2 with the latest Postgres 8.1 atabase (UTF-8 encoded); most of the initial Exponential setup went somewhat smooth until near the end of installation I receive a database application crash after table for "ezworkflow_process":

Excerpt from postgresql log (last three lines):
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "ezworkflow_group_link_pkey" for table "ezworkflow_group_link"
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "ezworkflow_process_pkey" for table "ezworkflow_process"
ERROR: invalid UTF-8 byte sequence detected near byte 0xf8

I have been informed that Postgres 8.1 is less forgiving about UTF-8 encodings. Has anyone crossed similar problems with Exponential 3.7.2 deployment and the latest Postgres 8.1. Might this be a bug or problem with the php scripts of Exponential 3.7.2? and perhaps has been corrected in the latest SVN stable release..

Oliver Pawellek

Saisung Corporation Ltd
www.saisung.com

Oliver Pawellek

Monday 09 January 2006 2:04:32 am

Please ignore my above recent post. I have just bumped into the Exponential documentation detailing the modification of files site.ini, i18n.ini and template.ini with "Charset=utf-8" within Exponential, and it appears to have cured the utf-8 database encoding dilemma.

Oliver Pawellek

Saisung Corporation Ltd
www.saisung.com