CMS Made Simple Forums

I just moved to a new hosting company and now my modules are not working properly, everything else seems okay. The old server had PHP 4.1.1 and MySQL 4-something-or-other. The new server has PHP 5.1.6 and MySQL 5.0.24. I'm suspecting this is where my problem lies but I'm not sure what to do about it. Specifically the modules I'm referring to are... FrontEndUsers-1.0.5, CMSMailer-1.73.9 and SelfRegistration-1.0.3. I'm running CMSMS-0.13.

When I log into admin the modules do not show in the menu nor on the modules page. CustomContent is the only one that shows up there. The modules are in the proper directory. When I try to reinstall them it just refreshes the page and nothing more appears. That is, installing them without overwriting what is there. I have data, or well, users registered on the site that I'd like to be able to retrieve without too much hassle if possible.

Any ideas? Tweaks??

Thanks.

You may be better off doing a fresh install to this new server then reinstall all modules and make sure they work then install Data Base Backup module on both sites, do a backup on original then do restore of it at new site...

I finally had time to get back around to this issue, mark, thanks for your reply.

What I actually did though was log into SSH and delete the module folders there that were not working. I then tried installing them again via the XML files, this did not work, same problem. So I deleted the folders again and just uploaded the folders themselves via FTP. This worked just fine... all of the templates were as I left them and all of the modules are working back to normal.

Thanks for your suggestion.

Maybe it will look stupid, but... did you check your permissions? I got my installation copied from one server to another. First, I had to change permissions on all writable directories, such as modules, tmp/cache, etc., because the ownership after copy was set to myself/mygroup, whereas cms runs under httpd's user and group, which are different. Already installed modules show as "unremovable", but to make them running I had to change their directory and file permissions, too.

When cms now installs a new module, its ownership is set to httpd-user/httpd-group and permissions are set to 770 (rwxrwx---), which means it is perfectly working but I cannot read any module file, e.g. when looking for bugs.

Hope it could help you.

Also, CMS-MS or FrontEndUsers data model (don't remember which one right now) contains a database table with an attribute named "when". This is pretty silly, because WHEN is reserved word in ANSI-SQL. The install script in the module will not create the table, because the attribute name "when" is not quoted (and even if it was, it is a silly idea... would you name your table or attribute "DROP"???), but the module installer does not notice at all there was an SQL error and does not report it. So you end up with a crippled module without knowing it. I suspect this might work on MySQL 4, for whatever reason, but it definitely does not work on MySQL 5, which seems to be more ANSI-SQL-compliant.

Good luck in debugging all the messy code!

Jindra

jindravavruska wrote:
Also, CMS-MS or FrontEndUsers data model (don't remember which one right now) contains a database table with an attribute named "when". This is pretty silly, because WHEN is reserved word in ANSI-SQL. The install script in the module will not create the table, because the attribute name "when" is not quoted (and even if it was, it is a silly idea... would you name your table or attribute "DROP"???), but the module installer does not notice at all there was an SQL error and does not report it. So you end up with a crippled module without knowing it. I suspect this might work on MySQL 4, for whatever reason, but it definitely does not work on MySQL 5, which seems to be more ANSI-SQL-compliant.

Have you filed this as a bug? if you haven't please do...

Yes, I did.

I like this system, but I think some parts could be coded more carefully. Thanks for your suggestion. Sometimes I have the feeling that nobody cares

Regards,
Jindra

Well we try

and if you do have a working solution for some problems please file a patch against current svn.

and 1.1 will have change a lot of stuff.. ted will probably announce it better in next few days...