Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi,

    Finally had a minute to check, sorry it was so long. Your way works just fine Gwolle. I didn’t think about security really, and as i said I am far from being expert.
    Thanks for your help.

    GReg

    Found one more:

    admin/editor.php line 197 – remove htmlentities and utf8_decode – that fixes entry editor.
    Is that it, or am I missing something else?

    GReg

    Ok,
    here is what I found:

    in what you used to print entries:
    echo stripslashes(htmlentities(utf8_decode($entry['entry_content']))

    I removed htmlentities and utf8_decode completely, thus leaving only:
    echo stripslashes($entry['entry_content']);

    that combined with UTF8 coding set in database tables solves the problem.

    I have done similar in frontend/read.php lines 149 (author name), and 158 (entry content); and in admin/entries.php lines 291 (content) and 304 (author name).

    I am not exactly an expert, but I guess it will work fine in most languages.

    It works for me, so I am happy now ?? hope it helps you as well.

    Thanks,
    GReg

    I have similar problem, using Polish characters this time. No errors were displayed, but specific letters change in question marks.
    I solved it partially: your (plugin’s) tables are set to latin1-swedish character set by default, I’ve changed them to utf8-general and in database they look as they should, but on blog still show as question marks.
    I’ll try to investigate it further tomorrow.

    GReg

Viewing 4 replies - 1 through 4 (of 4 total)