Followed README.txt to install in a properly running drupal site. (uses uri rewrite)

Run mysql -u -p < modules/ecommerce/store/store.mysql
Result successfull.

Navigated to administer -> modules. The page seems to try to load briefly, but stops with no result. It does not return the modules page. If I move ecommerce folder from modules directory, administer -> modules link works fine again. Checked database and ec_* tables are created.

thanks.

Menelaos Maglis (mmaglis)

Comments

mmaglis’s picture

mmaglis commented
Assigned: mmaglis » Unassigned
matt westgate’s picture

matt westgate commented

I think the above mysql statement is wrong since you didn't name the database to send the tables too.

I just tried a clean install of 4.5.1 and can't reproduce this. Here is what I did.

1. Added database definition files database.mysql and module/store/store.mysql to the database using phpmyadmin.

2. Created my first drupal account.

3. Navigated to administer > modules and everything loaded fine. (mod_rewrite enabled).

I can understand how this error might occur if trying to use the CVS HEAD version of the ecommerce package since it is not in sync Drupal HEAD yet.

mmaglis’s picture

mmaglis commented

Yes you are right. The statement is wrong for I typed in haste... I had executed it correctly thought, and I have veryfied the existance of ec_* tables in the database...

I checked it in another drupal system today and it seems to work properly this time. I do not know of any differences between the two systems but since this is not reproducable it should be closed.

Thanks anyway!

mmaglis’s picture

mmaglis commented
Priority: Critical » Normal

I had to open this up again for it bugs me!

I tried to install the entire ecommerce suite in the "problematic" site with the same effect as above.

I then tried to install ecommerce suite module by module (only adding one subdirectory at a time). This proved successful for all but two subdirectories = "tangible" and "contrib". On both of them (individually), I experienced the same effect as above (module section not loading at the admin site). Problem disappeared the moment those two directories were removed.

During the problem I checked apache2 logs to see of any trace of action. There was none! It seemed that when clicking the modules link, nothing happened.

This only happened in one of two sites I tried to install ecommerce suite, so I don't know what to do about it. It would be pain to re-install everything from scratch, as I don't see a reason for it...

kastaway’s picture

kastaway commented

Just had the same problem: after untarring the ecommerce directory, I could not load the modules page. Tried deleting subfolders under /modules/ecommerce. Doing a pair, like contrib plus address, worked. But then I tried disabling other modules, by moving them into /disabled_mods. That worked, too. I pinpointed the problem to blog.module, or blogapi.module, or locale.module.

Here is the weird part: eventually, within a couple minutes, I moved those three back into /modules as well. And everything works.

I think: I have been untarring module directories as root, and the resulting directories end up with owner 302:302, and I'm not sure with what permissions. I think maybe in copying them around, the umask changed the permissions, or maybe the owner info got changed. I don't know. And I'm probably not going to find out, at this point.

matt westgate’s picture

matt westgate commented
Status: Active » Closed (fixed)

You've probably run out of PHP memory. You'll need to either uninstall some modules or increase the memory_limit variable in php.ini.