Update from 1.2.1 to 1.2.2?

[orbon design]

Hi everybody!

I have a three language site (EN-NL-DE) which I would like to update to 1.2.2 because I really *love* the 'label' addition (www.site.com/language/index.php).  But I am a bit confused about the diff-update procedure from 1.2.1 to 1.2.2:

Here's what I know I should do:
- back-up the MySQL database;
- back-up the current site;
- update CMSMS to 1.2.2
- update MLE to 1.2.2

What's not clear however is:
- Do I need to change my current config_lang.php?
- What do I need to do with the config_lang.php.alby.label file?
- Do I need to perform any MySQL queries/changes in order to facilitate the update?

Sorry about these -most likely- trivialities, but I've searched/read everything, and I am not confident yet about the update...

Thanks very much in advance!

[alby]

I have a three language site (EN-NL-DE) which I would like to update to 1.2.2 because I really *love* the 'label' addition (www.site.com/language/index.php).  But I am a bit confused about the diff-update procedure from 1.2.1 to 1.2.2:

Here's what I know I should do:
- back-up the MySQL database;
- back-up the current site;
- update CMSMS to 1.2.2
- update MLE to 1.2.2

Full MLE contain whole CMSMS 1.2.2
Upgrade to new release and test. After modify your config_lang.php

What's not clear however is:
- Do I need to change my current config_lang.php?

If you want labels and not en_US, nl_NL, de_DE: yes

- What do I need to do with the config_lang.php.alby.label file?

This is an example. Substitute Italian with your German items and delete Francais and Australian.
Important are:
- 'block' for compatibility with your DB
- 'locale_cms' is old local key (en_US, nl_NL, de_DE)
- DEFAULT_LANG is one of new LABEL
- delete your mle/mle_admin cookie

- Do I need to perform any MySQL queries/changes in order to facilitate the update?

Sorry about these -most likely- trivialities, but I've searched/read everything, and I am not confident yet about the update...

No, if you have a working MLE and don't change 'block' you don't changes nothing in DB.
You must change DB if you want "extended" multilingual to metadata/description per page (read README.FIRST.extended)

Alby

[orbon design]

Hi Alby,

Thank you very much for your reply!

Full MLE contain whole CMSMS 1.2.2
Upgrade to new release and test. After modify your config_lang.php

I did the update to 1.2.2. However, in the site admin/back end pages it still says it's version "1.2.1 Bridgetown" in stead of "1.2.2 Hometown". So I assume something went wrong, but I have no idea what... Do you have any idea?

If you want labels and not en_US, nl_NL, de_DE: yes

I changed the config.lang.php.alby.label file (and renamed to 'config_lang.php') to the following:

define('DEFAULT_LANG', 'english');
$force_mle_default = false;

$hls = array(


'english' => array(
'block'=>'en',
'flag'=>'',
'text'=>'English',
'locale_cms'=>'en_GB',
),

'nederlands' => array(
'block'=>'nl',
'flag'=>'',
'text'=>'Nederlands',
'locale'=>'nederland',
'locale_cms'=>'nl_NL',
),
'deutsch' => array(
'block'=>'de',
'flag'=>'',
'text'=>'Deutsch',
'locale_cms'=>'de_DE',
),

);

The site doesn't seem to work with these changes... With the old config_lang.php it works fine. Do you see anything wrong with this?
Also, does it matter what my settings are in the 'config.php' with regard to 'internal_pretty_urls' and/or 'use_hierarchy'?

- delete your mle/mle_admin cookie

How can I do this? Where are these files located?

No, if you have a working MLE and don't change 'block' you don't changes nothing in DB.
You must change DB if you want "extended" multilingual to metadata/description per page (read README.FIRST.extended)

I believe I did these DB queries when updating to 1.2.1 EXT.

Again many -no doubt stupid- questions, but I seem to be forgetting something...

Thank you very much in advance!
Roy

[alby]

I did the update to 1.2.2. However, in the site admin/back end pages it still says it's version "1.2.1 Bridgetown" in stead of "1.2.2 Hometown". So I assume something went wrong, but I have no idea what... Do you have any idea?

Hummm, are you secure of your uploads? I think that a few files are not overwrite (check version.php date in cms_root folder for example).
Re-upload whole package

If you want labels and not en_US, nl_NL, de_DE: yes

I changed the config.lang.php.alby.label file (and renamed to 'config_lang.php') to the following:

define('DEFAULT_LANG', 'english');
$force_mle_default = false;

$hls = array(


'english' => array(
'block'=>'en',
'flag'=>'',
'text'=>'English',
'locale_cms'=>'en_GB',
),

'nederlands' => array(
'block'=>'nl',
'flag'=>'',
'text'=>'Nederlands',
'locale'=>'nederland',
'locale_cms'=>'nl_NL',
),
'deutsch' => array(
'block'=>'de',
'flag'=>'',
'text'=>'Deutsch',
'locale_cms'=>'de_DE',
),

);

The site doesn't seem to work with these changes... With the old config_lang.php it works fine. Do you see anything wrong with this?

Config is ok,
you MUST delete your browser cookie for works (in this cookie there are old values: en_GB, nl_NL, ... and not new label)

- delete your mle/mle_admin cookie

How can I do this? Where are these files located?

In your browser preferences. For example, in FF, are in Tools > Options > Privacy > Cookie > delete cookie of your domain

No, if you have a working MLE and don't change 'block' you don't changes nothing in DB.
You must change DB if you want "extended" multilingual to metadata/description per page (read README.FIRST.extended)

I believe I did these DB queries when updating to 1.2.1 EXT.

Ok, if you have 1.2.1 EXT and you apply new queries (for metadata and titleattribute)  it's ok, rename two files in lib/classes only (read README.FIRST.extended)

Alby

[orbon design]

Thanks a lot again!

Everything works fine now! The removal of the cookies did the trick! Mille grazie!

Hummm, are you secure of your uploads? I think that a few files are not overwrite (check version.php date in cms_root folder for example).
Re-upload whole package

I redid the upload, but still no "1.2.2" in the admin area. Then I checked the 'diff' package you've made, and it seems the 'version.php' file is missing...

you MUST delete your browser cookie for works (in this cookie there are old values: en_GB, nl_NL, ... and not new label)

As stated above: this did the trick!


I am still working on the rest of my issues (i.e. mod_rewrite)...

Ciao!
Roy

[alby]

Everything works fine now! The removal of the cookies did the trick! Mille grazie!

Hummm, are you secure of your uploads? I think that a few files are not overwrite (check version.php date in cms_root folder for example).
Re-upload whole package

I redid the upload, but still no "1.2.2" in the admin area. Then I checked the 'diff' package you've made, and it seems the 'version.php' file is missing...

  diff file is VS CMSMS original install. If you have old MLE you must upgrade with full package.

I am still working on the rest of my issues (i.e. mod_rewrite)...

ok, please report your result

Alby

[orbon design]

Just to let you know my site is working okay now (CMSMS 1.2.3)... not exactly like I would like (still some problems with mod_rewrite), but it will do for the time being (i.e. until CMSMS2)...

I am now using the following URLs: www.site.nl/index.php/english/contact.html
I figured it's SEF enough... 

Thanks for all the help!