Fresh install on Ubuntu 11.04 using

  • PHP memory limit 512 MB

These messages come up after the 95 modules get installed (after it gets to 100%):

The Date API requires that you set up the <a href="/?q=admin/config/regional/settings">site timezone and first day of week settings</a> and the <a href="/?q=admin/config/regional/date-time">date format settings</a> to function correctly.

Status message
Countdown Timer javascript file saved to: public://jstimer/timer.js
Error message
Notice: Undefined index: view date repeats in user_role_grant_permissions() (line 3028 of /var/www/modules/user/user.module).

SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null

I imagine the last one is fatal. Is there a fix in place for this?


d4v1d21’s picture

Have the same problem, then i try to follow an advise to change php.ini configuration Safe Mode=OFF.

matthoov’s picture

It looks like something is happening when trying to set permissions for the opendeals_module. I used this patch and was able to get around the failure.

wiifm’s picture

That patch simply drops the permissions that are yet not yet available to the system. Also it is a core patch (tisk tisk). I would suggest this would not solve the problem, simply hide it.

When making install profiles in the past, we encountered this same issue, how we got around it was to manually insert into the database the permissions (using db_insert()), rather than using the drupal API. I know this is also not that clean, but it at least guaranteed that the install profile would always work. We were encountering the issue as we were creating content types on install (using features), and the content types did not yet 'exist' in drupal, hence this error.

Any drupal opinions on the best solution to this. This surely must come up in every install profile that attempts to insert permissions for newly created content types.

nchar’s picture

Status: Active » Closed (fixed)

The bug is now fixed. You can download the beta 4 release and retry.

dagomar’s picture

The bug is now fixed. You can download the beta 4 release and retry.

How? It would be incredibly helpful if this was clarified.

dagomar’s picture

Issue summary: View changes