I am migrating my arabic content from old joomla 1.0.15 to new version of 1.5.13. When i migrate it shows characters like this "ÏÑÌÇÊ ÇáÍÑÇÑÉ ÇáÓäæíÉ " instead of arabic. In my new site arabic lanaguage is enabled.

In both servers the iconvlib library is enabled. Please help me as what exactly is the problem as the content items are more then 20000.

I am using PHP5.2.9 with mysql 5 in new version and PHP 4.4.9 and mysql 5 in new version.

I am using PHP5.2.9 with mysql 5 in new version and PHP 4.4.9 and mysql 5 in new version.

Does this mean you have PHP5+ on the new destination site.
If not I would suggest you look into upgrading as Joomla 1.5+ series will run much better under PHP5+

I am migrating my arabic content from old joomla 1.0.15 to new version of 1.5.13. When i migrate it shows characters like this "ÏÑÌÇÊ ÇáÍÑÇÑÉ ÇáÓäæíÉ " instead of arabic. In my new site arabic lanaguage is enabled.

This may be because the 1.0.15 site database is UTF8 encoding.

If this is the case you can make the following changes:

On the 1.0+ site go to:
/administrator/components/ com_export_content/convert_img.php
Where you will see two functions that should be changed to the below:




This is where the conversions take place so if you change it to the above all the data should be compiled without issue.

That said please make sure to check via the edit feature in export content before transferring.

Please post back with your results, thanks.

Thank you for your reply dear. Yes i am running PHP 5.2.9 on my new site.

I changed the two functions in the file convert_img.php with the two you provided. They were very long function so i just removed them and replaced with

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

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

and compiled the data. When i just clicked the 'View Compiled Content SQL installation File' the file showed me the title and introtext field like this below

"INSERT INTO #__export_content (`id`, `title`, `alias`, `title_alias`, `introtext`, `fulltext`, `state`,`sectionid`, `mask`, `catid`, `created`, `created_by`, `created_by_alias`, `modified`, `modified_by`, `checked_out`, `checked_out_time`, `publish_up`, `publish_down`, `images`, `urls`, `attribs`, `version`, `parentid`, `ordering`, `metakey`, `metadesc`, `access`, `hits`, `metadata`)VALUES('4549','������� ������ ������ - ������ ','','','<p align=\"right\">
<p align=\"right\">������ ��� ������ ���� ��� ����� ��� �� ���� ���� ����� ���� ������� ����� ��� ������� ������. ���� ���� ����� �� ���������:<br /> "

And when i installed that import_content_data zip file to the new joomla 1.5 website it showed a big error saying error 1064 but the content was imported. When i clicked export content to transfer the content the content looked liked scrumbled.

ãåÑÌÇä ãæÓßæ ÇáÏæáí ááÌÇÒ Ýí ÇáåæÇÁÇáØáÞ

Please see the attached picture of export content when i imported the data from joomla1.0.15.


Please tell me now what to do. I have more then 10000 articles. I have to migrate them in any case. please help me.

Is the source database utf8 encoding?

Have you tried going through the process with English as the default language?

When developing I only ever used English as I don't understand other languages.

On tests arabic languages seemed to import/export ok.

I think the issue will be something todo with database incoding or the PHP 4.4.9 on the old site.

Are you sure that you have export content 1.7.0 installed on the old 1.0+ site?
More info here

And are you sure iconv is enabled on the old site.
It is normally enabled by default under PHP5+ but not under PHP4+.

From PHPmyadmin of source database i got the following information

MySQL charset: UTF-8 Unicode (utf8)

Database Name:irhaltravelarabia(old website database) Collation:latin1_swedish_ci

Yes i had already exported and imported english content and that is working absolutely correct no problem. But when i compile arabic it creates problem.

Export content is 1.7.0 in old website.

chaltatv.com/phpinfo.php
Here you can see iconv is installed with php 4.4.9.

I also thing the problem is with old database incoding. Please see what can be done furthur.