Secure Permissions does not know that permissions have been exported [#843120]

CentOS 5.4
Apache 2.2.3
PHP 5.3.2 / 128M mem limit
MySQL 5.0.77
Drupal 6.17 (multisite installation)
Secure Permissions 6.x-1.1

1) Installed Secure Permissions in /site/all/modules
2) Enabled Secure Permissions module
3) Created role 'test'

4) Went to /admin/user/secure_permissions/export copied text
5) Created a .module file: /sites/all/modules/secure_permissions/custom_secure_permissions.modules
6) Pasted text into .module with a leading <?php

7) Created a .info file: /sites/all/modules/secure_permissions/custom_secure_permissions.info
8) Enabled Custom Secure Permissions module

9) Visited /admin/user/secure_permissions
10) Error: Your permissions have not been exported to code yet.

Any ideas on what I should start checking first?
[thanks agentrickard for your prior help]

Comment	File	Size	Author
#9	843120-easier-perms.patch	4.61 KB	agentrickard
#7	secure_permissions_with_better_instructions2.patch	1.72 KB	cos
#6	secure_permissions_with_better_instructions.patch	1.55 KB	cos
#5	843120-easier-perms.patch	3.75 KB	agentrickard
#3	secure_permissions.patch	6.77 KB	cos
#3	secure_permissions_housecleaning.tar_.gz	13.11 KB	cos

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

cos CreditAttribution: cos commented 2 July 2010 at 00:09

Solved problem. Named hook wrong. Doh.

I've done some housekeeping on the module to make it easier for others. Where should I send the suggested changes?

Comment #2

agentrickard

he/him

English

Georgia (US)

CreditAttribution: agentrickard commented 4 July 2010 at 17:52

Attach a patch here.

http://drupal.org/patch/create

Comment #3

cos CreditAttribution: cos commented 13 July 2010 at 05:41

File	Size
secure_permissions_housecleaning.tar_.gz	13.11 KB
secure_permissions.patch	6.77 KB

Comment #4

agentrickard

he/him

English

Georgia (US)

CreditAttribution: agentrickard commented 13 July 2010 at 13:21

Problem is, you can't provide a secure_permissions_data.module in the download tarball, because module updates would overwrite your custom file.

That's why we don't do this now. Yes, this module expects that you understand some advanced concepts, but it's targeted at developers who should be comfortable with the issues involved.

Other documentation improvements would be welcome.