By UNarmed on

Hey all, perhaps someone could help me out here.

More often than now when enable a module and click save i get the following error message. It even happens when i just place a module in my sites/all/modules folder. Its getting pretty frustrating =/

All my other pages work fine except the admin ones.

Fatal error: Maximum execution time of 30 seconds exceeded in C:\wamp\www\includes\common.inc on line 511

Help would be greatly appreciated!

Comments

mshepherd’s picture

mshepherd commented

To be clear; does this happen when you enable the module or when you simple place the module into the module folder?

UNarmed’s picture

UNarmed commented

Both, sometimes i place the module in the folder then once i enable it i get the error and other times i simply place the module in the folder and then when i click the administer section it happened (note this second one dosent happen as frequently).

The fact that it gives me the error when i enable a module bothers me the most.

Thanks

UNarmed’s picture

UNarmed commented

I am totaly stuck here man, if you have a possible solution you could offer i would realy realy appreciate it.

mshepherd’s picture

mshepherd commented

Hmmm...

For a start, I'd try try increasing the maximum execution time in your php.ini file. See here:
http://www.php.net/manual/en/info.configuration.php#ini.max-execution-time

Just guessing here, but it could be that the execution time is more than it should be because the php memory available isn't high enough. So look at increasing the memory available to php. See here:
http://drupal.org/node/29268

Give those a go and let us know what happens.

Good luck.

robbin.zhao’s picture

robbin.zhao commented

I suggest you to remove this module, and what's the module name? if it is not a core module, you can remove it from the all/modules folder, or changed the db values directly then remove the module.

you can use another same module instead of it

-
广州Drupal开发 - Drupal大学

UNarmed’s picture

UNarmed commented

Hey all thanks a lot for the help. I have found something that dose the trick.

Ok i open up the status report page and then in another window i open the modules page. Then enable the desired module and then save configuration, this stil gives me the error.

I then run cron from that status report page and it sorts it all out.

Bit of a mission but at least it gets the job done i suppose

Regards

nocks’s picture

nocks commented

I followed your approach and it did work for me. Thanks for sharing your approach of jumping the hurdle!