Hello all,

I uploaded e-commerce into my modules directory.
Checked "enabled" in the Administer>SiteBuilding>Modules page. (Token is also enabled.)
The confirmation page came back as a blank page.

I am now no longer able to get to the Modules page... it comes back blank as well.

E-commerce does show up under Administer and I can configure it... so it is installed.

Any suggestions?

Comments

forsythes’s picture

My logs are flooded with:

warning product 07/31/2007 - 12:50 No product types are available. webmaster

However, I cannot get to the module page to enable "products" if that's the right thing to do...

gordon’s picture

Status: Active » Postponed (maintainer needs more info)

I have taken a look at this and it is because you have no product modules like generic or tangible installed. But I am unable to replicate this on my system, or even on a completely new install of Drupal

DeweyOxberger’s picture

I can reproduce the problem. Yikes, the admin/modules/list/confirm page is empty.

My system in a fresh install on a Linux box.

php 5.2.0, apache 2.2.3

All of this was downloaded and installed on Aug 6, 2007:

I installed Drupal 5.2, did some config, Worked fine.

Installed German, Spanish, French translations. Worked fine.

Installed the i18n module (Internationalization), did some config, worked fine.

Installed Meta-tags module (nodewords), did some config, seemed to work fine.

Installed token and ecommerce, went to admin/modules and checked token. Then I clicked the commit changes button (no ecommerce enabled yet).

admin/modules/list/confirm is a blank page.

I did a rm -R token to delete it from the modules directory. Then I tried to go into admin/modules and it was still a blank page. I did a rm -R ecommerce and now admin/modules is up and running again.

I'll keep poking around and see if I can narrow it down a bit.

DeweyOxberger’s picture

I need to be more clear: once in the broken state admin/modules and admin/modules/list/confirm are blank.

Once in that state doing rm -R ecommerce (and leaving token there) will return access to admin/modules.

DeweyOxberger’s picture

Forgot to mention - I'm ecommerce 3.3.

In my apache error log I see:

[Wed Aug 08 10:51:22 2007] [error] [client 192.168.5.40] PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 43318 bytes) in /home/web/public_html/includes/common.inc on line 2176, referer: http://archive.cirris.com/en/admin/build

So is this a php memory configuration issue? A memory leak? Is 16Meg a reasonable amount?
Is there any kind of config I need to tinker with to help nail this down?

DeweyOxberger’s picture

More parts to the behavior - with my (now suspect) installation: if I untar token into my modules directory then the module admin page shows just fine but if I enable Token the confirm page is blank. The admin/build/modules page shows just fine.

rm -R token and it's back to normal operation with both admin/build/modules showing and admin/...list/confirm showing.

DeweyOxberger’s picture

This looks like a php memory issue - not really a bug. I have way too many features enabled and php needs more memory. It looks like a core-only drupal needs 8-10M and by they time you add i18n and Meta tags modules you are at 16M.

I'm on linux so I went into

/etc/php5/apache/php.ini

and changed

memory_limit = 16M to 32M and now everything seems to be running just fine.

I just hope my ISP is willing to do that...

gordon’s picture

Version: 5.x-3.2 » 5.x-3.3
Status: Postponed (maintainer needs more info) » Fixed

Yes as you confirmed it is a memory issue. The modules page does use a lot more memory than other pages, so you will need to increase the amount of memory per session so that you can enter this page.

The amount of memory required all depending on how many modules you have installed, also I am found that a lot of memory is required just to compile the php, so using something like APC or eAccerater dramatically reduces the amount of required memory once cached.

I have found that just compiling the code for caching on a a basic install of Drupal is about 8-10Mb, when as with eAccelerator running after it is cached it will drop to just over 1Mb of memory per session.

I actually run eAccelerator on all my systems, including my development machines.

Anonymous’s picture

Status: Fixed » Closed (fixed)
kangghee’s picture

Just have to re-open this thread because the memory limit is becoming quite crazily large!

I have to change the php.ini from

memory_limit = 128M
to
memory_limit = 256M

That's quite large a limit I must say. And it is quite a clean installation too. Only just added the token module, and nothing more. Oh and I am trying to test the Ubercart module, not exactly the eCommerce module we're discussing in this thread. Nevertheless, the solution is found here.

Thanks people!

claudio.lente’s picture

For me ... it is a memory issue.

I moved my install from Windows to Linux system.

After saw blank screen, find this solution on forum.

In Windows my PHP.ini
memory_limit = 256 M ; original é 128 M
post_max_size = 32M ; original é 8M
upload_max_filesize = 32M ; original é 2M

In Linux, after blank screen, i changed values to same PHP.ini settings (above) and all work!

My Drupal is 6.10, PHP 5.1.6.

Thanks all.