On 9 Feb 2011, at 01:28, rick c wrote:
Do the non-ascii characters cause an error when used in a post?
If I have debugging on, the text area gets filled with the error
information. If I have debugging off, the text area (where I'm
inputting the content of the post) simply goes blank, and on the site
the content is blank. I can see what I have entered only if I look in
the database directly.
You say it is on a different site. Are the two sites on different
servers? If so, what db backend are each of them using.
Both sites are on the same sever. db backend is MySQL.
PHP version 5.3.0
MySQL version 5.0.67
I've tried the text you pasted in a comment on a site running r4862,
SQLite, PHP 5.3.3, Ubuntu 10.10. There were no errors.
I have been modifying quite heavily the site that is giving me the
error, so it is quite possible that I have done something
inadvertently to break it. It has more plugins installed (some I have
modified) and a more customised theme than the site which is OK.
I fear I may have to re-trace all my steps to find out where I've gone
wrong :-(
Philip
Rick
On Feb 8, 1:47 pm, Philip Buckley <[email protected]> wrote:
It came to light when someone typed an English pound sign, £. I then
tested it with a French e acute as I guessed it was an issue with
non-
ascii characters, and indeed that too errored. Here is a pastebin of
some text that will error <http://pastebin.com/AbXjBmK8>
Thanks
Philip
On 8 Feb 2011, at 18:22, Chris Meller wrote:
I don't know of any changes off hand, but can you pastebin somewhere
the content you're using that's causing the problem so we have
something to test with?
On Feb 8, 2011, at 11:03 AM, Philip Buckley wrote:
Hi,
I am getting this error when I save a post containing non-ascii
characters:
htmlspecialchars(): Invalid multibyte sequence in argument
in
system/classes/utils.php:1088
The version of Habari is: Habari 0.7-alpha r4806
I am working on another site on which I don't get the error. That
is running Habari 0.7-alpha r4628. I wondered if anyone can
immediately think of a change that has been made between those two
revisions (end of November to end of January) that might account
for the error?
Of course, it might well be that I have done something myself to
break it!
Any pointers appreciated
Thanks
Philip
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group athttp://groups.google.com/group/habari-dev
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group athttp://groups.google.com/group/habari-dev
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
