Blank screen when trying to install certain modules

[fuzzcore]

Hey everyone, I'm new to CMSms and did a fresh install of v0.13(canary).

Everything worked fine, but when I tried to install a few modules by copying the files into the cms/modules-directory, I get a blank screen in admin->extensions->modules.
This happens everytime I install any of the following modules: Album, FrontEndUsers, galleryS, . I was able to install the Calendar-module and PunBB this way however.
I don't understand how this is possible, is this a known problem? I only find topics about blank pages after initial install when searching the forums, but nothing about my case, can someone help?

[Punktraum]

Hi

I have exactly the same Problem with some other modules (for example "BlankOfTheMonth", "Content Aliases"). Some other ("GoogleMaps", "PISearch) works fine!

I get the blank screen only in admin->extensions->modules, the other sections will be displayed without styling (but works)!  .

- CMS Made Simple 1.0.1 "Oahu" (switched to german language).
- Folder Permisson on Module Folder - 777
- Upload with FTP

Thanks for help.

[calguy1000]

If you check your server logs, you'll probably find that php is running out of memory, and you'll have to bump the php memory_limit up.

[Punktraum]

OK, i will check the logs.

But, i'm able to install different Modules without any limitations, the problems causes only some of them.
And the site as well as the other functions in the admin-panel works fine (and fast).

[Punktraum]

After enabling the logs i received the following error:

Fatal error: Class 'CMSModuleContentType' not found in
/path/to/cmsms/installation/modules/BlankOfTheMonth/BlankOfTheMonth.module.php on line 550

Line 550 in BlankOfTheMonth.module.php:

Code: Select all

class BlankOfTheMonthModule extends CMSModuleContentType

Memory allocated for PHP: 32 MB
PHP version: 5.0.4
BlankOfTheMonth module version: 1.0
CMS Made Simple 1.0.1 "Oahu"

Any ideas?

[Jellybean]

I had the same problem.  If you delete the module you install - delete the whole folder, you will get back your styling.  THis doesn't solve the problem of actually installing the module.  For the Content Aliases module does not work with the latest release so don't bother installing it.

[tsw]

Some modules havent yet updated to use 1.0 specific stuff and will most probably brake stuff.

If you find such a module I suggest you create a bug for that module and maybe even send email to the developer.

[SwordFishTromBones]

This errors seem consistently to do with the modules not finding the CMSModuleContentType class.
I've noticed that it's moved from class.module.inc to class.content.inc in the versions concerned.

I'm not a php guy at all but is there an include missing somewhere along the line due to the change in class location which is causing so many modules to fail?

The online API is still showing it as defined in module as well !