Has anyone else encountered this, and/or is able to suggest a fix?
[After trying to save a node:] DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 at ../lib/Wiki/Toolkit.pm line 895
On Wed 18 Apr 2007, Earle Martin openguides@downlode.org wrote:
Has anyone else encountered this, and/or is able to suggest a fix?
[After trying to save a node:] DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 at ../lib/Wiki/Toolkit.pm line 895
Can you send the content that you were trying to write to the node, so we can have a look at it? Or is it something you found in your weblogs?
Kake
On Wed, 18 Apr 2007, Earle Martin wrote:
Has anyone else encountered this, and/or is able to suggest a fix?
[After trying to save a node:] DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 at ../lib/Wiki/Toolkit.pm line 895
Try adding:
# ...the encoding that your database uses? (blank if default) dbencoding = utf8
to your wiki.conf
Nick
On Wed, Apr 18, 2007 at 02:01:10PM +0100, Earle Martin wrote:
Has anyone else encountered this, and/or is able to suggest a fix?
[After trying to save a node:] DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 at ../lib/Wiki/Toolkit.pm line 895
Either set postgres to not use unicode for that database, or make sure that all the content is utf-8 before inserting it.
I think that browsers should encode post content in the same charset as the page that served the form, so setting the content-encoding to utf-8 on all your pages might do it.
Cotswoldguide has this problem I think.
Hope that helps
David
On 18/04/07, Kake L Pugh kake@earth.li wrote:
On Wed 18 Apr 2007, Earle Martin openguides@downlode.org wrote:
Has anyone else encountered this, and/or is able to suggest a fix?
[After trying to save a node:] DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 at ../lib/Wiki/Toolkit.pm line 895
Can you send the content that you were trying to write to the node, so we can have a look at it?
Unfortunately I lost it in a browser crash, but the only possible culprit I could think of would be the £ symbol, which seems unlikely. I replaced it with £ to no effect. I'll try and recreate the case again when I have some time, probably tomorrow.
Cheers,
E
On Wed, 18 Apr 2007, Earle Martin wrote:
Unfortunately I lost it in a browser crash, but the only possible culprit I could think of would be the £ symbol, which seems unlikely. I replaced it with £ to no effect. I'll try and recreate the case again when I have some time, probably tomorrow.
Try with a pound sign, before and after setting the dbencoding flag (you might need to reload the edit page after setting it). I think setting dbencoding to utf8 should fix it for you, as that's what I had to do for the cotswolds openguide
Nick
On Wed, Apr 18, 2007 at 04:53:55PM +0100, Earle Martin wrote:
On 18/04/07, Kake L Pugh kake@earth.li wrote:
On Wed 18 Apr 2007, Earle Martin openguides@downlode.org wrote:
Has anyone else encountered this, and/or is able to suggest a fix?
[After trying to save a node:] DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 at ../lib/Wiki/Toolkit.pm line 895
Can you send the content that you were trying to write to the node, so we can have a look at it?
Unfortunately I lost it in a browser crash, but the only possible culprit I could think of would be the £ symbol, which seems unlikely.
For the record, in my mail reader (which fails on anything outside of latin-1, or maybe ascii ;)), this says "? symbol", which lets me know that it's not in the standard range 0 - 127 range... So I think that this is a possible culprit worth investigating.
Regards,
openguides-dev@lists.openguides.org
-
Christopher Schmidt -
David Sheldon -
Earle Martin -
Kake L Pugh -
Nick Burch