CMSMS_MLE is this the right place to ask for install help...

[sarah_h]

.. if not I apologise and please point me in the right direction.

I've just installed CMS Made Simple 1.2.3 "Black Rock" (from the forge) for the MLE functionality and I've followed the how to's to help with the ML setup. I've also viewed the video help. So, I've renamed the config_lang.php.alby to config_lang.php (or should that be config.lang.php?) The word how to suggests the latter but either way I get the same result. I've applied the SQL changes to the content_name and menu_text to add the langs I'm working with i.e. content_name_en and content_name_fr and the same for the menu text. I've added html_en and html_fr to the htmlblobs.

My config_lang.php looks like this:

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

$hls = array(

'en_US' => array(
'block'=>'en',
'flag'=>'',
'text'=>'English',
'parent'=>'en',
),
'fr_FR' => array(
'block'=>'fr',
'flag'=>'',
'text'=>'Français',
),
);


BUT I'm still seeing a 404 error when I try to view the site. Now I don't think I've missed anything and the only thing which confuses me is the lang selectors i.e. I've used 'en_US as the default lang to use but the DB just uses en. Should I be doing something differently here? There's one other thing. I notice that I don't see the 'collation' field in phpmyadmin. I see Field, Type, Attributes instead of Fild, Type, Collation, Attributes!

I hope someone can alert me to my errors.

Thanks

Sarah

[alby]

.. if not I apologise and please point me in the right direction.

I have move in this forum

I've just installed CMS Made Simple 1.2.3 "Black Rock" (from the forge) for the MLE functionality and I've followed the how to's to help with the ML setup. I've also viewed the video help. So, I've renamed the config_lang.php.alby to config_lang.php (or should that be config.lang.php?)

Drop last extension .alby only => config_lang.php

The word how to suggests the latter but either way I get the same result. I've applied the SQL changes to the content_name and menu_text to add the langs I'm working with i.e. content_name_en and content_name_fr and the same for the menu text. I've added html_en and html_fr to the htmlblobs.

Check your content table vs:

Code: Select all

CREATE TABLE `cms_content` (
  `content_id` int(11) NOT NULL,
  `content_name` varchar(255) collate utf8_unicode_ci default NULL,
  `content_name_en` varchar(165) collate utf8_unicode_ci default NULL,
  `content_name_fr` varchar(165) collate utf8_unicode_ci default NULL,
  `type` varchar(25) collate utf8_unicode_ci default NULL,
  `owner_id` int(11) default NULL,
  `parent_id` int(11) default NULL,
  `template_id` int(11) default NULL,
  `item_order` int(11) default NULL,
  `hierarchy` varchar(255) collate utf8_unicode_ci default NULL,
  `default_content` tinyint(4) default NULL,
  `menu_text` varchar(255) collate utf8_unicode_ci default NULL,
  `menu_text_en` varchar(165) collate utf8_unicode_ci default NULL,
  `menu_text_fr` varchar(165) collate utf8_unicode_ci default NULL,
  `content_alias` varchar(255) collate utf8_unicode_ci default NULL,
  `show_in_menu` tinyint(4) default NULL,
  `collapsed` tinyint(4) default NULL,
  `markup` varchar(25) collate utf8_unicode_ci default NULL,
  `active` tinyint(4) default NULL,
  `cachable` tinyint(4) default NULL,
  `id_hierarchy` varchar(255) collate utf8_unicode_ci default NULL,
  `hierarchy_path` text collate utf8_unicode_ci,
  `prop_names` text collate utf8_unicode_ci,
  `metadata` text collate utf8_unicode_ci,
  `titleattribute` varchar(255) collate utf8_unicode_ci default NULL,
  `tabindex` varchar(10) collate utf8_unicode_ci default NULL,
  `accesskey` varchar(5) collate utf8_unicode_ci default NULL,
  `last_modified_by` int(11) default NULL,
  `create_date` datetime default NULL,
  `modified_date` datetime default NULL,
  PRIMARY KEY  (`content_id`),
  KEY `content_alias` (`content_alias`,`active`),
  KEY `default_content` (`default_content`),
  KEY `parent_id` (`parent_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

My config_lang.php looks like this:

Ok

BUT I'm still seeing a 404 error when I try to view the site. Now I don't think I've missed anything and the only thing which confuses me is the lang selectors i.e. I've used 'en_US as the default lang to use but the DB just uses en. Should I be doing something differently here?

block is for compatibility with old MLE.
- you can use block 'what you want this' in DB, different name for each lang BUT use parent for PARENT lang
- en_US is "locale" lang (CMSMS load this lang PHP file) or use 'what you want here' BUT use locale_cms for point the exact locale PHP file
View config_lang.php.alby.label for full sintax

404 happens for: trouble in DB (check with phpmyadmin) or if you modify your config_lang.php (CLEAR cookie for your site)

There's one other thing. I notice that I don't see the 'collation' field in phpmyadmin. I see Field, Type, Attributes instead of Fild, Type, Collation, Attributes!

You have a old version of phpmyadmin OR old version of mysql
Try with last version of phpmyadmin and for mysql at least 4.1

Alby

[sarah_h]

Thank you Alby for taking the time to reply. It is much appriciated.

I will update to more recent version of phpmyadmin and I will look over this post again.

I'll post back here when I know more.

Thanks again

Sarah

[sarah_h]

Hi,

Here's an update on my findings. I'm using the MLE version CMS Made Simple 1.2.3 "Black Rock" DL from the Forge.

I followed all the install instructions from the video tutorial using CASE B and the 'Mini Howto MLE - Installation/Upgrade' and changed the SQL to follow Alby's sample i.e. content_name and menu_text.

Now when I tried the site then I did not see a 404 error and the pages were there but without any page names (links). So I went into admin and added page names for the English and French pages. The admin side seems to work ok, the lang flags are visible and I get no errors.

When I tried the site then I got the 404 error! I not cannot return to a working site!! Why the 404?

I getting quite desperate now and the only things I'm a little confused about are the lang arrays in config (what does 'block' mean. Do they look ok to you?) and that in the DB there's a 'Collation' field which I cannot see! Is this because I'm using an older version of MySQL 3? Could that be causing problems?

can anyone check that these look ok;

This is my config:

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

$hls = array(


'en_US' => array(
'block'=>'en',
'flag'=>'',
'text'=>'English',
'parent'=>'en',
),
'fr_FR' => array(
'block'=>'fr',
'flag'=>'',
'text'=>'Français',
),
);

And this screenshot shows the changes.

Please help!

Sarah

[sarah_h]

Hi again,

Well I have some success! This is what I did.

1. I started fresh with DL from forge of CMS Made Simple 1.2.3 "Black Rock".

2. I installed and made sure that it was working first, en only at this point.

3. I read README_FIRST again and followed Alby's instructions to the word (almost!). This time I left the langs as they are in the readme i.e. en, fr, it. Originally I removed 'it' from the list.

4. I ran the SQL queries, but this time instead of inserting them manually like last time I ran the query in phpmydmin SQL but because I could not see the any ref to CHARACTER or COLLATE I removed them from the query before I ran them. So this is how is was:

ALTER TABLE `cms_content` ADD `content_name_en` VARCHAR(165) CHARACTER SET utf8 COLLATE utf8_unicode_ci NULL AFTER `content_name`;

and after

ALTER TABLE `cms_content` ADD `content_name_en` VARCHAR(165) NULL AFTER `content_name`;

Now, I'm using an old version of MySQL 3.5.3 and could not see CHARACTER SET and COLLATE. I removed them from each query for the 'content_name', 'menu_text' and 'html_blobs' just to see what would happen! I don't know what problems this will give me yet!

5. Then I ran the query UPDATE `cms_content'.

6. I did not run the queries on `cms_content_props` as Alby says this part is optional.

7. I then renamed config_lang.php.aby to config_lang.php (I've read some help docs which uses config.lang.php. This is not correct, note the dot, should be an underscore).

8. And then I tried the site. It worked but the menu titles were missing so into admin to add the menu names, try again and it worked!!

9. To get the lang selectors on the front end just add {lang} to your templates

So that's how I got it to work, I suppose I just followed the instructions really with a couple of minor changes! I expect I'll have some more questions though. But I'm happy now and grateful for all your help/advice.

[alby]

Now, I'm using an old version of MySQL 3.5.3 and could not see CHARACTER SET and COLLATE. I removed them from each query for the 'content_name', 'menu_text' and 'html_blobs' just to see what would happen! I don't know what problems this will give me yet!

Arghh... 3.5.3 it's very very very old!
I have a site also with 3.23.58 and there are NOT these commands
The best use is with versions 5.X (actual version) where there is full support for utf-8

EDIT: my bad language....

Alby

[sarah_h]

So would that cause the problems I'm talking about do you think?

[alby]

So would that cause the problems I'm talking about do you think?

In my opinion were not taken properly sql queries for errors in commands (I have correct my prev post)
In README.FIRST:

MySQL 5.0.X with utf8_unicode_ci, in sql query check and change SET and COLLATE if not

Alby