Content problem

[christiaans]

Hey alby,

I am running a mle install successfully, but I ran into a small (actually kinda big) problem.

I had 7 languages at the start, but had to add 3 more afterwards. That worked fine and all, but the thing is, the languages that I added afterwards, copy the content from the English pages (however, NOT in the database). Usually it just results in an empty page, so that I can leave the unfinished items from the menu, but it does display them, with the English content (English is the main language ofcourse).

Do you know how I can fix this, because on the last three languages, I want to just have 1 page instead.

You can see the wip on: http://www.blindspot-solutions.eu/content/
(The last three languages that I added are Russian, Swedish and Hungarian.)

Just to simplify what I mean: when a page in Russian, Swedish or Hungarian is empty, it takes the English content and uses it for that specific page. But I do NOT want that, since I want just one page for these languages. How can I solve this?

[christiaans]

I tried some things, and have not succeeded so far, any one?

[alby]

I tried some things, and have not succeeded so far, any one?

Have you checked in content.content if you have all langs content_block?
And a new page?

Alby

[christiaans]

I'm not quite sure what you mean actually.

I have repeated all the steps in the readme files (normal & extended).

However, I might have gone wrong at this point:

UPDATE `cms_content` SET `prop_names`= REPLACE(`prop_names`,'content_en','content_en,content_it,content_fr') WHERE `prop_names` LIKE '%content_en%';

(that is the standard readme SQL query)

and I turned that into this:

UPDATE `cms_content` SET `prop_names`= REPLACE(`prop_names`,'content_en','content_en,content_it,content_fr,content_nl,content_es,content_pl,content_de,content_ru,content_sv,content_hu') WHERE `prop_names` LIKE '%content_en%';

Could this be the problem?

Also, this is the SECOND time I followed the readme, to add ADDITIONAL languages!

[alby]

I'm not quite sure what you mean actually.

I have repeated all the steps in the readme files (normal & extended).

However, I might have gone wrong at this point:

UPDATE `cms_content` SET `prop_names`= REPLACE(`prop_names`,'content_en','content_en,content_it,content_fr') WHERE `prop_names` LIKE '%content_en%';

(that is the standard readme SQL query)

and I turned that into this:

UPDATE `cms_content` SET `prop_names`= REPLACE(`prop_names`,'content_en','content_en,content_it,content_fr,content_nl,content_es,content_pl,content_de,content_ru,content_sv,content_hu') WHERE `prop_names` LIKE '%content_en%';

Could this be the problem?

Also, this is the SECOND time I followed the readme, to add ADDITIONAL languages!

The query is correct BUT must be run ONE time only. If you add other languages the correct (about because order is important but it's for understand) query is:

UPDATE `cms_content` SET `prop_names`= REPLACE(`prop_names`,'content_en,content_it,content_fr,content_nl,content_es,content_pl,content_de','content_en,content_it,content_fr,content_nl,content_es,content_pl,content_de,content_ru,content_sv,content_hu') WHERE `prop_names` LIKE '%content_en%';

if content_ru,content_sv,content_hu are new languages

You must check cms_content table with a sql tool (phpmyadmin for example) and check in prop_names if you have 1 lang_block only (ex: content_it) for ALL languages


Alby