Magento Module install SQL not running

Question

I have written a module that is refusing point blank to create the tables within my mysql4-install-1.0.0.php file....but only on the live server.

The funny thing is that on my local machine (which is a mirror of the live server (i.e. identical file structure etc)) the install runs correctly and the table is created.

So based on the fact that the files are the same can I assume that it is a server configuration and or permissions problem? I have looked everywhere and I can find no problems in any of the log files (PHP, MySQL, Apache, Magento).

I can create tables ok in test scripts (using core_read/write).

Anyone see this before?

Thanks

** EDIT ** One main difference between the 2 environments is that on the live server the MySQL is remote (not localhost). The dev server is localhost. Could that cause issues?

Can you add other modules, e.g. the developer toolbar or something else known not to screw up a system? If so then the problem is with your module not the setup of MySQL etc. — ʍǝɥʇɐɯ
– ʍǝɥʇɐɯ, Commented Jun 30, 2011 at 15:53
Later versions of Magento (1.6+ I think) look for an install-1.0.0.php file, rather than a mysql4-install-1.0.0.php file. — Andy Triggs
– Andy Triggs, Commented Mar 3, 2014 at 14:31

Community · Accepted Answer · 2017-05-23 12:13:32Z

5

Is the module which your install script is a part of installed on the live server? (XML file in app/etc/modules/, Module List Module for debugging.)
Is there already a record in the core_resource table for your module? If so, remove it to set your script to re-run.
If you file named correctly? The _modifyResourceDb method in app/code/core/Mage/Core/Model/Resource/Setup.php is where this file is include/run from. Read more here

edited May 23, 2017 at 12:13

CommunityBot

11 silver badge

answered Jun 30, 2011 at 15:56

Alana Storm

167k96 gold badges422 silver badges623 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

sulman Over a year ago

Thanks Alan. 1) Yep, I’m confident that all the required module files are installed correctly on the live server (as it is replicated from the dev server). 2) I am removing the listing in the db to test. 3) I will have a look at this function and debug. Thanks

Marc B · Accepted Answer · 2011-06-30 15:34:16Z

3

Probably a permissions issue - a MySQL account used by public-facing code should have as few permissions as possible that still let it get the job done, which generally does NOT allow for creating/altering/dropping tables.

Take whatever username you're connecting to mysql with, and do:

SELECT User, Host
FROM mysql.user
WHERE User='your username here';

This will show you the user@host combos available for that particular username, then you can get actual permissions with

show grants for username@host;

Do this for the two accounts on the live and devlopment server, which will show you what permissions are missing from the live system.

answered Jun 30, 2011 at 15:34

Marc B

362k44 gold badges433 silver badges508 bronze badges

3 Comments

sulman Over a year ago

Thanks for the reply. The live system has GRANT ALL for my user so I guess the MySQL permissions are more than enough. Thanks though.

ʍǝɥʇɐɯ Over a year ago

I think this is off the mark because Magento uses its own connector to access the database.

Marc B Over a year ago

Doesn't matter how magento connects, if it's a permissions issue, then this is how you'd compare the permission sets between the two systems. Just because magento has its own connector doesn't mean it can magically bypass the MySQL grant system.

ʍǝɥʇɐɯ · Accepted Answer · 2011-06-30 15:52:05Z

1

In the Admin->System->Advanced section is your module present and enabled?

Did you actually unpack your module to the right space, e.g. app/code/local/yourcompany/yourmodule ?

Do you have app/etc/modules/yourmodule.xml - I believe that this could be the overlooked file giving rise to your problem.

answered Jun 30, 2011 at 15:52

ʍǝɥʇɐɯ

4,0128 gold badges34 silver badges53 bronze badges

2 Comments

sulman Over a year ago

Thanks for the reply. Yes everything appears to unpack correctly and the module appears in the admin correctly. As mentioned the file structure is identical to the dev server and it installs correctly on that. Thanks.

ʍǝɥʇɐɯ Over a year ago

Is it registered already? Open phpmyadmin and search for your module name. It will be in a config table, just the one key. Take it out and then it should magically install itself.

dancl · Accepted Answer · 2013-03-17 17:46:10Z

1

the cache could be the culprit, if you manually deleted the core_resource row for your module in order to make the setup sql run again, you have to also flush the cache

probably a difference between dev and production servers is cache settings, that would explain why you only see this in production

answered Mar 17, 2013 at 17:46

dancl

7275 silver badges13 bronze badges

Comments

arsdever · Accepted Answer · 2019-11-29 05:53:14Z

0

For me, the issue appeared using Windows for development. Linux system is case sensitive. In my config.xml the setup section was named camelCase while the folder was named all-lowercase. Making them the same made the script run.

edited Nov 29, 2019 at 5:53

arsdever

1,3041 gold badge13 silver badges39 bronze badges

answered Nov 28, 2019 at 20:38

Lyubomir

3196 silver badges14 bronze badges

Collectives™ on Stack Overflow

Magento Module install SQL not running

5 Answers 5

1 Comment

3 Comments

2 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

1 Comment

3 Comments

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related