Attach checklists to entities as fields

Thank you, @mmartinov; that's a clever patch. My concern here is that checklist progress is currently stored in Drupal persistent variables, and since those all get loaded into memory on every bootstrap in Drupal 7, that could quickly become a performance problem for sites of any scale. I like the idea, though—it's actually been on my own wishlist for a bit. I think that how I'd like to accomplish it is to make Checklists entities that can be attached to content types as fields. That will be a big job, though, and won't come through soon. In the meantime, if you understand the implications of your patch and you know it won't be a problem in your use case, you could probably go ahead and use it yourself. If you have any experience with entities and fields and would like to help out there, I would welcome that, too. Best wishes!

@mmartinov, what if we had a little offline conversation about entities? Contact me.

Subscribing for the entity feature cause using the variables for this is not really nice.

Updated patch.

re. #2, what would be the benefit of defining Checklist entities? It seems like a simpler solution would be to just define a Checklist field type. This would get us db-backed storage when attached to entities, but we could leave the existing implementation for global checklists. It seems like it'd at least be a step in the right direction, and make converting to entities later easier.

The attached patch implements checklists as fields. The site-wide checklists remain unchanged, so it shouldn't break any APIs. It provides a simple select widget, to choose from among the defined checklists, and the formatter simply displays the checklist form.

Thanks for the patch, @ergonlogic! I'm excited to look at it, but I'm indisposed this week. I'll give it a look as soon I'm able.

Note that the attached patch for field support should also fix #1966114: Add support for per-user saved progress.

Fixed trailing whitespace in patch.

After a bit more use, here are a few more things to look at as part of adding support for checklists as fields:

• Rather than clutter up the ChecklistapiChecklist class, maybe we should add a ChecklistapiChecklistField class that inherits from it, then overrides the necessary bits for fields support. I think this would mostly entail adding getSavedProgress() and setSavedProgress methods that would be called from __construct() and saveProgress() respectively.
• That, in turn would allow easier cleanup of a couple remaining todos in clearSavedProgress() and hasSavedProgress().
• We probably need per-checklist-per-entity-type permissions: '[view|edit] the <checklist_title> on <entity_type>', and so a new access function is probably in order.

This patch addresses the first item from #12, adding a ChecklistapiChecklistField class that inherits from ChecklistapiChecklist, etc.

Still to do:

• Clearing saved progress on checklist fields still needs work, as the menu and confirmation form need to be reworked to allow the entity id and field delta to be passed in.
• Also, the new perms still to be added and checked.

Just an observation. If a Checklist Item was an entity (not specifically the list itself) then you could do some really cool stuff with views by querying on items that have been cleared or not on certain days and what not.

Commit 8a7a128f8 in my sandbox fixes the remaining todos from #13. We end up with lots of permissions, but that's the price of flexibility.

Hi, I was wondering, has this in some way been ported to drupal 8, or is it planned?
Would there still be performance issues in trying to doing it?

Thanks!

@fourmi4x: This patch has not been ported to Drupal 8 unless someone has done so on the side. I would still like to pursue making checklists into fields, but I wouldn't take the approach in this patch. I don't personally expect to have the time to work on it in the foreseeable future, though.

I am interested in doing something along the lines of what @generalredneck describes in comment #14 above, using the Log module (http://drupal.org/project/log) for the individual checklist item entities. I created a new issue to explore that idea in more detail: #2876152: Integrate with Log module - input and ideas would be welcome!

I would love to see a module that can attach checklists to entities. @m.stenta: How far are you with your project?

@LaurensV: I'm working towards a tight project deadline right now, and checklist integration may or may not end up being part of it. If it is, then I will likely be creating entities from checklists, rather than the other way around. Specifically, this will be my approach: #2876152: Integrate with Log module

If that doesn't happen during this project, I may still pursue it in the future, but I'm not sure when.

I know this is an old thread, but I needed some similar functionality to attach a checklist to an entity and ended up doing something using entity references and borrowing heavily from the UI of checklist api, but for a different use case.

https://www.drupal.org/project/checklist_entity_reference

Not sure if there would be any way to make checklist api do this sort of thing, if so I don't want to duplicate effort.

Thanks, @andy_w. You're not duplicating effort. There's no way to do what you're accomplishing with Checklist API itself today.

Also, marking this "Needs work", since the latest patch would need to be ported to Drupal 8 before it could be reviewed.

Closing this in favor of #3474212: Create a new architecture for checklists as config entities, with tasks fulfilled by conditions.

Actually, the fieldable use case may actually be out of scope for that issue. Let's call it a dependency instead.