Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Trying to use module grants with SPACES modules I get these errors:
- warning: array_fill() [function.array-fill]: Number of elements must be positive in E:\server\drupal\includes\database.inc on line 253.
- warning: implode() [function.implode]: Invalid arguments passed in E:\server\drupal\includes\database.inc on line 253.
- warning: array_keys() [function.array-keys]: The first argument should be an array in E:\server\drupal\modules\user\user.module on line 502.
- user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1
query: SELECT p.perm FROM role r INNER JOIN permission p ON p.rid = r.rid WHERE r.rid IN () in E:\server\drupal\modules\user\user.module on line 502.
Comments
Comment #1
RdeBoerHi MXT,
To help me reproduce the errors and debug can you tell us which version of http://drupal.org/project/spaces you're using? Is it 6.x-3.0-beta4 ?
Thanks!
Comment #2
cwaring CreditAttribution: cwaring commentedI'm experiencing the same issues described against Spaces-6.x-3.0-beta4 (with spaces_og enabled). I haven't tested any other version as I'm running a fresh install.
Comment #3
RdeBoerJust wondering whether anyone tried this recently with the latest versions of Module Grants and Spaces as both modules have undergone some changes.
I have installed Spaces (and Features and Context etc.) and haven't seen any of the errors above, yet. Mind you I haven't used it in earnest, so any tips as to what pages generate the above errors would be welcome.
Comment #4
RdeBoerComment #5
marcus178 CreditAttribution: marcus178 commentedI'm getting the same error as well on an Open Atrium install.
Here's what I have installed
Spaces 6.x-3.0
Module Grants 6.x-3.6
Taxonomy Access Control 6.x-1.2
Basically trying to get Taxonomy Access Control working with OG which this module does until I get this error and can't view any content.
Comment #6
marcus178 CreditAttribution: marcus178 commentedSorry to pester but any ideas on how to fix this.
Just in case it's relevant I'm also using OG 6.x-2.1
Comment #7
RdeBoer@marcus178, #6
I understand your frustration, but with D7 ports and all that I currently don't have time to look at this as a first priority.
I will revisit, but not in the next couple of weeks.
Sorry.
Maybe someone else has time to dig deeper into this.
Comment #8
danillonunes CreditAttribution: danillonunes commentedI have the same error. Think this patch fixes it. Someone can test it and confirm please?
Comment #9
danillonunes CreditAttribution: danillonunes commentedOh, sorry, the patch above is the one I used on my project vcs.
That's the correct one.
Comment #10
danillonunes CreditAttribution: danillonunes commentedHaha, just uploaded the wrong patch again... Now the correct.
Comment #11
danillonunes CreditAttribution: danillonunes commentedAlso, marking as needs review.
Comment #12
RdeBoerThanks for the patch danillonunes! Nice and easy too.
Will include in the next release.
Comment #13
RdeBoerPatch applied to Git master branch. Will be available in 6.x-3.7.
Comment #15
MrAdamJohn CreditAttribution: MrAdamJohn commentedWe are working on a site that has robust use of Spaces and began working in the Content Access elements, including the much anticipated use once again of the most celebrated Module Grants module. Unfortunately, immediately upon enable we encountered errors (even user 1) on all pages.
These errors recur with small line number changes, as noted below. We are using;
Spaces 3.4 (most recent at this time)
Module Grants 3.8 (most recent at this time)
Perhaps there is some remaining spaces/module grants interaction issue?
Any help would be appreciated.