next »

[CrazyArmyCat]

Hi all,
Having a problem with my installation, I hope I have included all the necessary information. I have installed this once before without a problem. But this time it's on a different server.

I get to step 5 and get this fatal error:

Updating hierarchy positions...[done]

Setting up core events...[done]

Installing modules...
Fatal error: Call to a member function on a non-object in D:\hshome\bla\bla\lib\classes\class.globalcontentoperations.inc.php on line 85


I am trying to install cmsms-mle-1.0.2-build4 (multi)

MySQL client version: 4.1.15

Server: Localhost via UNIX socket

I hope that is enough info...could really use some help.

thanks!

[Pierre M.]

Hello,

the 1.0.2-MLE is unsupported. You may find information about it in the German forum.

See the trouble shooting section of the installation guide about "Fatal error: Call to a member function on a non-object".
Check FTP logs.

Are you on Windows with IIS ?

Pierre M.

[CrazyArmyCat]

Hi Pierre,
thanks for the help...Ya, I can't read anything in the German forum I will check the installation guide tonight. I am on a windows server... Do you think the simplest solution would be to switch to Linux?

[Pierre M.]

If you can switch to Linux hosting, why haven't you already ?-)

BTW, there is a unofficial release today of an unsupported continuation of the MLE fork.

Pierre M.

[CrazyArmyCat]

Hi Pierre,
Can't transfer to Linux...I need a multilingual site, would a possible solution be to install the latest 1.1.1 and when 2.0 comes out update it without loosing my data?

thanks,

[Pierre M.]

Hello,

unless you can maintain/migrate yourself, you shouldn't use unsupported forks.
The safest is to run the current stable official release, 1.1.x today, 2.0.x someday.

Pierre M.

[CrazyArmyCat]

If i need a multilingual site I guess I have to wait for 2.0.

[cyberman]

Please read this thread

http://forum.cmsmadesimple.org/index.php/topic,14461.msg73353.html#new

Alby has created a MLE version based on current CMSms.

And there exists a thread in forum for modifying database ...

[alby]

Please read this thread

http://forum.cmsmadesimple.org/index.php/topic,14461.msg73353.html#new

Alby has created a MLE version based on current CMSms.

And there exists a thread in forum for modifying database ...

In file README.FIRST (in root distribution) there are all sql query for trasform a normal CMSMS site (monolingual) in MLE

Alby

[cyberman]

In file README.FIRST (in root distribution) there are all sql query for trasform a normal CMSMS site (monolingual) in MLE

Thx. Haven't use/read them  ...

[CrazyArmyCat]

I did a clean install of cmsms-mle-1.1.2 and everything looked great. I modified the config_lang.php.alby and renamed it to config_lang.php. The admin pannel looks good (flags etc..) But now I get a "page cannot be found" for index.php. What am i missing?

[alby]

I did a clean install of cmsms-mle-1.1.2 and everything looked great. I modified the config_lang.php.alby and renamed it to config_lang.php. The admin pannel looks good (flags etc..) But now I get a "page cannot be found" for index.php. What am i missing?

Have you read README.FIRST and apply all sql querys?
If you rename config_lang.php.alby in config_lang.php your db MUST be in MLE mode.

Alby

[CrazyArmyCat]

Hi Alby,
For the sql querys, I was able to make the change for number I. in the README.FIRST file but i am confused on what to for number II. and III.

any help will be really appreceated.

[alby]

Hi Alby,
For the sql querys, I was able to make the change for number I. in the README.FIRST file but i am confused on what to for number II. and III.

Ok,
a. I suppose (for example) that you want: en_US, it_IT and fr_FR
b. and relative blocklanguage are (prev compatibility with MLE 1.02): en, it and fr
(Same of config_lang)

II. After install of 1.1.2 in prop_names column of cms_content there is content_en (this is because CMSMS is monolingual)
With:
UPDATE `cms_content` SET `prop_names`= REPLACE(`prop_names`,'content_en','content_en,content_it,content_fr') WHERE `prop_names` LIKE '%content_en%';
substitute content_en with content_en,content_it,content_fr (i.e. your content_blocklanguage, see b. for blocklanguage)


III. In cms_content_props tables there is content_en (this is because CMSMS is monolingual)
You must enter new rows relative to 'content_it' and after 'content_fr' for ALL items of content_en:

For content_it:
INSERT INTO `cms_content_props` (`content_id`,`type`,`prop_name`,`param1`,`param2`,`param3`,`content`,`create_date`,`modified_date`)
    SELECT `content_id`,`type`, 'content_it' ,`param1`,`param2`,`param3`,`content`,`create_date`,`modified_date`
    FROM `cms_content_props` WHERE `prop_name` = 'content_en' AND `type` = 'string';

For content_fr:
INSERT INTO `cms_content_props` (`content_id`,`type`,`prop_name`,`param1`,`param2`,`param3`,`content`,`create_date`,`modified_date`)
    SELECT `content_id`,`type`, 'content_fr' ,`param1`,`param2`,`param3`,`content`,`create_date`,`modified_date`
    FROM `cms_content_props` WHERE `prop_name` = 'content_en' AND `type` = 'string';

English isn't my language, if there are errors please correct me

Best regards
Alby

[CrazyArmyCat]

Thank you very much for your help Alby. It is working perfectly now