Checkboxes Disabled

Give UID1 a role and switch on "update ajax checklists" permission for that role. Right now it only checks that permission and does not auto-allow UID1.

Anton

I'm having exactly the same problem but with version 5.

I am at version 6.x-1.0 and I can manipulate the checkboxes after which the affected line shortly turns red (somehow indicating that they are probably saving to DB). And the checkbox stays checked. So this looks allright to me.

But when I open the node again. Nothing has saved. And the node is untouched.

I have given my admin user the permission to change/edit the Ajax Checklist. But still to no avail.

Please can anyone point to how do I change the state of the box AND save it to DB?

Thanks

Morten E

Anyone - This is driving me mad.

Please help...

Thanks

Morten

I spent a little time going through this module, and there are a couple of things that can cause the checkboxes to misbehave. I'm documenting what I found here, to help others in diagnosing problems such as the one excaliburst is having.

First, if the checkboxes appear as "[cb ....", then your node's text isn't being modified by the input filter. Check your input format configuration, check the format selected on your node, and check the filter order within your input format. Subsequent filters can modify the output of previous filters, and this can be hard to diagnose. I found it useful to set up an input format that only applies the AJAX checklist filter, and use this for testing.

Next, if the checkboxes appear, but are disabled (grayed out), the javascript file is probably not attached to the page. View the page source and look for "ajax_checklist.js" in a <script> tag near the top. This needs to be present for the checkboxes to work.

Third, if the checkboxes appear, but their behavior is flaky -- for example, you can check the checkbox, but it doesn't turn red while saving, or if the wrong boxes are checked when you load the page -- it's possible the node id isn't being written to the <form> and <input> tags that define the checkbox. View the page source and look for these tags; the <form> tag should specify 'id="##"', where "##" is a node id; if text appears here, then the token isn't being replaced with the actual node id when the page is rendered. The node id should also appear as the "value=" attribute in the <input> tag that follows the <form> tag.

The upshot is this: the page is well-formed if (1) the .js file is attached, and (2) node ids appear in the <form> and <input> tags for each checkbox.

I made some changes to the module to make sure the .js is attached on the right pages, to make it less likely that other modules will interfere with the node id token replacement, and to let checkboxes work on CCK fields. I've attached a patch. Here's what changed:

• The node id is placed in the <form> and <input> tags in a preprocess function instead of ajax_checklist_nodeapi(). That seems to let checkboxes work with CCK fields. I changed the token to !ajax_checklist_nid, to look more like the tokens used with the t() function; the old token format was being filtered out by other modules.
• The .js file is attached to the page in ajax_checklist_nodeapi() in the "alter" operation, and only if the rendered node body contains the token. The means the .js file is loaded only where needed.
• I added an implementation of hook_filter_tips(), so users can see an example checkbox syntax on node edit forms.
• Table references in sql queries are "prefixed" (surrounded by curly braces).
• Some light editing on text.

This is a great module, BTW. Exactly what one of our sites needs -- but also a nice example of what you can do in Drupal. Thanks to AsciiKewl for contributing this!

Attaching source for the page

I had this same issue with the checkboxes being disabled. My installation was in a subdirectory so the ajax calls were failing. You can check if this is your problem by using Firebug > Net and look at the ajax calls for ajaxchecklist.

I have modified the path in #9 so that it removes entries from the table on node delete and user delete. Note: this module does not handle node revisions, so any changes to the checks are the same for all revisions.

Attached is the patch for js and module files, so apply from your modules directory.