Import/Export pluggin encoding problem

[ntorres]

Hi

I'm using ojs 2.1.1 and it works fine until I change the server which hosted it.

When I visit the journal home page and access to published issues I have no problem; even when the editor access to an issue or article. But when I use the import/export plugin to export data I get an encoding error.

Using the navigator can can't read the xml file, and if save the xml file using the mouse right button I get a file with encoding problems.

Can anyone help me?

[jmacgreg]

Hi ntorres,

Can you tell us exactly which error you are getting?

Cheers,
James

[ntorres]

Hi,

The problem is that the xml file generated uses a bad encoding for the issue and article data. For example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE issue PUBLIC "-//PKP//OJS Articles and Issues XML//EN" "http://pkp.sfu.ca/ojs/dtds/native.dtd">
<issue published="true" current="false">
<title>Vol.: 1 Núm.: 1</title>
<volume>1</volume>
...
and not
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE issue PUBLIC "-//PKP//OJS Articles and Issues XML//EN" "http://pkp.sfu.ca/ojs/dtds/native.dtd">
<issue published="true" current="false">
<title>Vol.: 1 Núm.: 1</title>
<volume>1</volume>
...

When the file is showed using the browser, depending which kind of browser (Explorer, Firefox, Chrome) and versions the error is different and matches with the first strange character found. As the file will contain bad encoded information it can't be used for the purpose for which it was exported.

[jmacgreg]

Hi ntorres,

You can find more information on character encoding here. Additionally, you should still be able to save and subsequently edit any XML file you export, regardless of errors, although the strange characters will still show up. You may also want to double-check that when you changed the server, you recreated the database on the second server to match the database character encoding on the original server. Let us know if none of this advice helps out.

Cheers,
James

[ntorres]

Hi James,

to recreated the database on the second server I use a mysql dump from the first server that includes the create database sentence, so the two databases would be equals. It's an estrange problem because it only appears when you use the import/export plugin... when the database content is showed in other ojs page there are no problem.

[jmacgreg]

Hi ntorres,

I suspect that this may be a bug in your version of OJS, but I'm having trouble tracking a relevant report down. Is there any chance you could try upgrading to a more recent version?

Cheers,
James