enable module
phicarre - December 3, 2006 - 23:06
| Project: | RoleAssign |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | TBarregren |
| Status: | closed |
Jump to:
Description
when i try to enable the menu i have the following message:
"An illegal choice has been detected. Please contact the site administrator."
#1
The module works as expected with both Beta 1 and 2 out of the box. Thus, you must have done something non-trivial that cause this error of yours.
If I should be able to help you, you must provide me with a lot more information. Which version of Drupal 5.0 are you running (some pre-beta, Beta 1 or Beta 2)? Which moduels have you installed? And so on. But most important of all, you must give me a detailed description of necessary steps to repeat your bug. Before you send me this information, try to isolate the cause by turnig non-core modules off one by one.
For som suggestion on how to make an effective bug report, please read:
#2
I run 5 beta 2
I added : Roleassign module, widgEditor module, Front Page module
When I enable the rolleassign module then I have my famous message. idem fot the widgeditor module.
No message with the frontpage module.
I run PHP 4.4.4 not the 5.x version
#3
I am sorry that I haven't had time to look further into this before now.
I have followed your description and installed widgEditor 5.x-1.x-dev as of January 20 and RoleAssign 5.x-1.0 on a fresh Drupal 5.1. First I enabled the widgEditor module and then the RoleAssign module.
Your error occurred when you enabled the RoleAssign module. But I didn't notice any error. For me, everything work as expected.
You tested widgEditor with PHP 4 in spite of the fact that widgEditor requires PHP 5. Also, your problem occurred with beta 2 of Drupal.
Do you still get the same error when running Drupal 5.1 on PHP 5? If you do, could you provide me with detailed description of necessary steps to repeat your bug; from installing Drupal 5 to enabling RoleAssign.
#4
Since I haven't got any further details, I assume this is not a problem anymore. I therefore close the issue. Don't hesitate to reopen it if necessary.