Hi Jonathan(@jonathanshaw), how are you? I've been facing a similar issue. I implemented a custom handler with checkboxes, but when saving the node for the first time, the values aren't stored in the database. However, if I edit the node and save again, the checkboxes are saved correctly.
I haven't found a solution yet. I saw your comment #67, but what you mentioned didn't work for me.
Do you know any way to address this issue? I would really appreciate any help.
Best regards.
Hello,
I've been using module and would like to discuss the inclusion of an additional `hook_update_N()` that runs during module updates. I have specific concerns regarding the performance impact this additional process might have, especially on sites with a large number of nodes.
Including an update process that also triggers a permissions rebuild concerns me, as sites which may not need this update are forced to undergo a potentially costly process across a large number of nodes.
My questions and concerns are as follows:
1. What is the justification behind the inclusion of the additional `hook_update_N()`, aside from the install and uninstall processes? I understand there may be valid reasons, but I would like to better understand the context and necessity from the development team's perspective.
2. Has the performance impact of this additional process been considered, especially since the primary updates seem intended for installation and uninstallation scenarios? Recommendations for mitigating impacts on sites that may not directly benefit from this update would be highly appreciated.
Thank you for your time, and I'm open to further discussion on this topic.
Best regards,
Gonzalo2683 → made their first commit to this issue’s fork.
Gonzalo2683 → made their first commit to this issue’s fork.
mlncn → credited Gonzalo2683 → .