By mpapet on

Hi,

I'm posting this in Post installation because I didn't get a reply from the installation issues forum.

I've got two issues.

1. Core drupal 4.7.current.tar.gz works great, but *every* extra module added has failed. I have all of the core files owned by a user useraccount and group useraccount. file permissions are 644 and they all work great. I cannot do the same when I add modules. If I make them owned by the apache group, they at least appear as a module, but I can't configure them or see them in the admin menu.

2. I'm using postgresql. Is that why the modules are failing? If so, where do I find the error logs because they aren't coming up in the drupal error logs.

Any help would be great.

⋅ Categories: Drupal 4.7.x

Comments

cog.rusty’s picture

cog.rusty commented

Where do they "appear as a module" if you can't "see them in the admin menu"?

mpapet’s picture

mpapet commented

http://www.mydomain.com/?q=admin/modules I can enable/disable there.

What happens with some modules is after permitting access, they appear in my Administer menu where they can be configured.

But, I can't configure any new modules. Only the ones that came with the original package.

After screwing around with it some more, new modules aren't creating the tables for the database and giving no errors of any kind in the drupal administration interface. This suggests to me that permissions aren't right, but the only posts mentioning permssions/ownership have "it depends" as an answer.

cog.rusty’s picture

cog.rusty commented

Well, some modules do not create any tables and some do not have a configuration menu.

But maybe there is a problem.

There is only one way to find out. Let's check one particular module that you installed and does not work, to see what it didn't do.

mpapet’s picture

mpapet commented

Okay,

I tried installing the review module http://drupal.org/project/review which requires the votingapi http://drupal.org/node/36041

The votingapi actually generated an error once the permissions were changed.
"query: SELECT * FROM votingapi_action_set WHERE parent_name = '' ORDER BY weight, name ASC in /home/friend/public_html/includes/database.pgsql.inc on line 113." was the error.

I manually created the tables in pgsql and it cleared the error. Enable/disable and then access control options when enabled are there, but that's all I've got.

No errors for either module reported in drupal admin. Because of votingapi not creating tables, I checked for review tables and found none. I created those tables manually by the useraccount that drupal uses. This suggests it's not a db permissions issue. But I'm open.

Thanks for walking me through this.

cog.rusty’s picture

cog.rusty commented

As far as I can tell there is no file permission issue. Since the modules appear in admin/modules, they can be read.

Taking a look at their .install files, the problem seems to be that these modules do not create tables for pgsql. Only mysql and mysqli.

You could try to modify their .install files to include a case 'pgsql' but I am not sure what you should do differently in the pgsql statements (if anything), and also I am not sure if you would encounter other problems later with pgsql while using these modules.

If you try to go this route, you would need to delete the tables and the two lines in the 'system' table for these two modules, so that their start their installation from scratch.

-----------

An update: Someone has already done that for the votingapi module. I found this in its issues queue.

http://drupal.org/node/87238

mpapet’s picture

mpapet commented

I patched the votingapi.install and it still didn't do the job.

I think it comes down to most modules being wholly incompatible with pgsql.

I'm flushing pgsql and starting over with mysql.

cog.rusty’s picture

cog.rusty commented

In any case, don't forget to delete the module's line from the 'system' table if you want it to start over installing from scratch. Otherwise it will think that it is already done.

mpapet’s picture

mpapet commented

It looks like I had a number of mistakes in my php.ini configuration. The handbook has php.ini options, but the INSTALL.txt files don't mention them.

I also did some more specific createdb options that might have helped.

votingapi.install is definitely broken for pgsql-8.1 but other modules, it looks like I'm going okay. For now, I'm running two sites, one in mysql and one pgsql and comparing.

Thanks for all of your help.

I'm going to post my changes to the devel list on the INSTALL.txt files. They really should mention the php.ini configs in the INSTALL.txt file.

cog.rusty’s picture

cog.rusty commented

Maybe, but most people are on shared hosts who have no access to php.ini, so the INSTALL.txt cannot rely on requirements for php.ini except if they are very common settings.

Most of the php settings for Drupal are done either in settings.php with ini_set() calls or in .htaccess with php_value statements.