I just installed cck-6.x-2.1.tar.gz module and when I go read the modules Drupal goes blank. I do not know what to do.
I had the white screen of death happened before but if I refresh a couple of times it comes back.
I might remove the cck module and refresh to see if it comes back.
I think is pretty amazing that it is consider normal that Drupal goes to La, Land
Thanks,
Nesto r:-)
This is actually a php thing, not a Drupal thing. It usually means some php file (could be a module, theme, custom block) is throwing an unrecoverable error. I'm guessing it's not cck.
On Thu, Feb 12, 2009 at 5:32 PM, Néstor rotsen@gmail.com wrote:
I just installed cck-6.x-2.1.tar.gz module and when I go read the modules Drupal goes blank. I do not know what to do.
I had the white screen of death happened before but if I refresh a couple of times it comes back.
I might remove the cck module and refresh to see if it comes back.
I think is pretty amazing that it is consider normal that Drupal goes to La, Land
Thanks,
Nesto r:-)
-- [ Drupal support list | http://lists.drupal.org/ ]
I log out and then logged back in and it is working now. I had notice that before, where Drupal gets lost and if I logout and log in then Drupal clear its memory and it is ready to go.
It might be a PHP thing but Drupal is base on PHP and if a module is downloaded from the Drupal site it should not cause problems.
Not knowing enough about Drupal, I think that if you load several modules at a time then Drupal gets confuse. I also noticed that when I load a module and if it has several things to select, is better not to choose all of them at once because it is bound to go blank on you.
Thanks,
Nestor ;-)
On Thu, Feb 12, 2009 at 4:39 PM, Brett Evanson brettev@gmail.com wrote:
This is actually a php thing, not a Drupal thing. It usually means some php file (could be a module, theme, custom block) is throwing an unrecoverable error. I'm guessing it's not cck.
On Thu, Feb 12, 2009 at 5:32 PM, Néstor rotsen@gmail.com wrote:
I just installed cck-6.x-2.1.tar.gz module and when I go read the modules Drupal goes blank. I do not know what to do.
I had the white screen of death happened before but if I refresh a couple
of
times it comes back.
I might remove the cck module and refresh to see if it comes back.
I think is pretty amazing that it is consider normal that Drupal goes to
La,
Land
Thanks,
Nesto r:-)
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Brett Evanson brettev@gmail.com 801-599-0584 -- [ Drupal support list | http://lists.drupal.org/ ]
Could it be a time out type of problem? Could it be that it takes Drupal longer to respond than the amount of time that the Apche web server is willing to wsit?
OK, I just took a look at my apache error_log file and says: "PHP error: Maximun execution time of 30 seconds exceeded in Drupal\includes\common.inc on line 1831, referer: http://localhost/drupal/admin/build"
How do I change this?
Thanks,
Nestor :-)
On Thu, Feb 12, 2009 at 4:46 PM, Néstor rotsen@gmail.com wrote:
I log out and then logged back in and it is working now. I had notice that before, where Drupal gets lost and if I logout and log in then Drupal clear its memory and it is ready to go.
It might be a PHP thing but Drupal is base on PHP and if a module is downloaded from the Drupal site it should not cause problems.
Not knowing enough about Drupal, I think that if you load several modules at a time then Drupal gets confuse. I also noticed that when I load a module and if it has several things to select, is better not to choose all of them at once because it is bound to go blank on you.
Thanks,
Nestor ;-)
On Thu, Feb 12, 2009 at 4:39 PM, Brett Evanson brettev@gmail.com wrote:
This is actually a php thing, not a Drupal thing. It usually means some php file (could be a module, theme, custom block) is throwing an unrecoverable error. I'm guessing it's not cck.
On Thu, Feb 12, 2009 at 5:32 PM, Néstor rotsen@gmail.com wrote:
I just installed cck-6.x-2.1.tar.gz module and when I go read the
modules
Drupal goes blank. I do not know what to do.
I had the white screen of death happened before but if I refresh a
couple of
times it comes back.
I might remove the cck module and refresh to see if it comes back.
I think is pretty amazing that it is consider normal that Drupal goes to
La,
Land
Thanks,
Nesto r:-)
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Brett Evanson brettev@gmail.com 801-599-0584 -- [ Drupal support list | http://lists.drupal.org/ ]
OK, I changed the max-execution-time to 120 from 30 seconds and the memory-size-limit to 258 from 128 megs.
It takes awhile but it seems to be working, with only the CCK Content selected..humm
I tried choosing all the other CCK selections and it failed.
then I tried just CCK 'content' again and it work.
Then added CCK 'content copy' and it work.
I might just have to do them one of the selections at a time...what a hassle.
:-)
On Thu, Feb 12, 2009 at 4:52 PM, Néstor rotsen@gmail.com wrote:
Could it be a time out type of problem? Could it be that it takes Drupal longer to respond than the amount of time that the Apche web server is willing to wsit?
OK, I just took a look at my apache error_log file and says: "PHP error: Maximun execution time of 30 seconds exceeded in Drupal\includes\common.inc on line 1831, referer: http://localhost/drupal/admin/build"
How do I change this?
Thanks,
Nestor :-)
On Thu, Feb 12, 2009 at 4:46 PM, Néstor rotsen@gmail.com wrote:
I log out and then logged back in and it is working now. I had notice that before, where Drupal gets lost and if I logout and log in then Drupal clear its memory and it is ready to go.
It might be a PHP thing but Drupal is base on PHP and if a module is downloaded from the Drupal site it should not cause problems.
Not knowing enough about Drupal, I think that if you load several modules at a time then Drupal gets confuse. I also noticed that when I load a module and if it has several things to select, is better not to choose all of them at once because it is bound to go blank on you.
Thanks,
Nestor ;-)
On Thu, Feb 12, 2009 at 4:39 PM, Brett Evanson brettev@gmail.com wrote:
This is actually a php thing, not a Drupal thing. It usually means some php file (could be a module, theme, custom block) is throwing an unrecoverable error. I'm guessing it's not cck.
On Thu, Feb 12, 2009 at 5:32 PM, Néstor rotsen@gmail.com wrote:
I just installed cck-6.x-2.1.tar.gz module and when I go read the
modules
Drupal goes blank. I do not know what to do.
I had the white screen of death happened before but if I refresh a
couple of
times it comes back.
I might remove the cck module and refresh to see if it comes back.
I think is pretty amazing that it is consider normal that Drupal goes
to La,
Land
Thanks,
Nesto r:-)
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Brett Evanson brettev@gmail.com 801-599-0584 -- [ Drupal support list | http://lists.drupal.org/ ]
Quoting Néstor rotsen@gmail.com:
I log out and then logged back in and it is working now. I had notice that before, where Drupal gets lost and if I logout and log in then Drupal clear its memory and it is ready to go.
That is true for any website that controls the sessions of authenticated users.
It might be a PHP thing but Drupal is base on PHP and if a module is downloaded from the Drupal site it should not cause problems.
I wouldn't say that. The contributed modules are what others think are handy dandy tools. Some have better developers and maintenance methods than others. Some *you* end up debugging before you can use them. Always test modules in development before moving them to production.
Not knowing enough about Drupal, I think that if you load several modules at a time then Drupal gets confuse. I also noticed that when I load a module and if it has several things to select, is better not to choose all of them at once because it is bound to go blank on you.
The problem with selecting a large amount of new modules to activate is the install process. Nearly all the modules will install a table or two and creating tables will take some time. If your PHP limits are set to factory default or less and you choose several modules you could easily reach the stop processing threshold. This isn't a Drupal issue it is a system configuration issue. Both Apache, PHP and MySQL (or whatever DB you use) need tuned to meet your needs.
-- Earnie http://r-feed.com Make a Drupal difference and review core patches.