Hi Steve,

An update: I was unable to use your suggestion for the SQL commands on the new site, as the odd character was showing up for multiple instances (dashes, question marks, ellipses, an array of things). What I did do, however, was use your suggestion to track down improperly encoded characters from the original site (the site where I exported the content) and then change them to the correctly encoded format. I then re-exported all of the data, and reimported everything again on the new site. Voila! It worked.

Thanks so much for your suggestion. While it did take me a while to get through it all, it was much less of a headache than it would have been to copyedit each imported document by hand.

I appreciate your help!

Carly

i have the same problem with importing from/into joomla 1.0.13 and 1.0.14

example

There is no need to establish a community recreation node
around Torakina Park  it is already happening. Plans in this precinct
for commercial development near the surf club and accommodation on
land south of the club are also worrying.

Hi tlearyus

Export Content seems to have picked some control character or ms word.

I have attached a patch that should sort out the problem.

Download it locally and unzip it then replace:
/administrator/components/com_export_content/convert_img.php with the new one.
Then re-compile and see how it goes.

many thanks - really appreciate it !!

will let you know how it goes.

cheers - tlearyus

sorry but it didn't work, added the updated file to my current Joomla setup and did an export

then did a fresh joomla 1.0.14 install on a new host, installed the latest SVN release of Joomla export and imported the content by sections and still getting all the strange chars.

would love to get this working so let me know what you need to help fix this.

cheers - glen

ooops - double post.

Hi Glen

QUOTE:
i have the same problem with importing from/into joomla 1.0.13 and 1.0.14

Please give me more details to make sure we are on the same page.

Are you trying to move content between to sites from the Joomla 1.0+ series like 1.0.13 for example or from 1.0+ to 1.5+.

If so what language are the sites in.

If they are Latin based (English for example) and you are moving between the 1.0+ Joomla series you may be able to use the old Export Content version 1.6

You may also find this thread useful.
http://www.bestdownloadsites.com/export_content/component/ option,com_fireboard/Itemid,13/func,view/id,926/catid,1/

Hi,

Great comments on this component. Although my encoding problems do not appear to be going away.

My setup: -

From:
Joomla 1.0.14
Export Content 1.7

To:
Joomla 1.0.14
Export Content 1.7

I am exporting a section that has items containing

Code:

 

amongst other things like apostrophes ('. Without any changes to the component: The content component installs ok, but the

Code:

 

code gets re-written to control chars as well as other stuff going wrong. When your patch is applied: The content component will not install, due to control characters in the content. When removing all code from the numeric_html & high_order functions to return $text unchanged: The content component will not install, due to control characters in the content. Is there a way to get this component to transfer the content "as is", so I do not have to edit the content the other end? I am happy to make changes to the code and will even attempt to re-write the component if necessary. Just as a matter of course, would the whole issue of encoding go away if you just base64 encoded the whole lot before putting it in the xml file. Then base64 decode the whole lot on extraction? Thanks, Copiermad

Hi Copiermad.

QUOTE:
Is there a way to get this component to transfer the content "as is", so I do not have to edit the content the other end? I am happy to make changes to the code and will even attempt to re-write the component if necessary.

Just as a matter of course, would the whole issue of encoding go away if you just _base_64 encoded the whole lot before putting it in the _xml_ file. Then _base_64 decode the whole lot on extraction?

I have been thinking about by passing the XML by writing all the data to a separate file that may be executed after the install process this would do away with the whole issue of trying to parse characters via XML.

The only thing is finding the time as I'm very busy with another large paying project.
If you want to give it a go by all feel free and please post back here so it can be shared with the rest of the community.

Your idea about base_64 encoding may be the way to go for you at the moment to get out of trouble the only issue is that it will make the upload size larger and therefore restrict how much can be moved at one time other than that I see no problem with it.

If you want to give it a go the best way to go about it would be to change:
administrator/components/com_export_content/convert_img.php

Code:

function numeric_html($text){}

to do the encoding. And in /administrator/components/com_export_content/admin.export_content. About line 2000 you will see:

Code:

function multiSectionSave( $option, $cid) {}

This is where after the content has been installed and you want to transfer by sections. As you scroll down you will see that there is a decoding function this is where you could do the base_64 decoding:

Code:

$sect_title = decode_entities($sect->title);

The decode_entities() function is about line 2500 of /administrator/components/com_export_content/convert_img.php One other thing I would remove everything in the high_order function as instructed earlier in this thread.

Code:

function high_order($text){ return $text; }

Please post back with any questions.

Another thread that may help.

Changing encoding