Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Add support for Inline Entity Form to lock and unlock referenced node entities when a user "edits" them inline.
Comment | File | Size | Author |
---|---|---|---|
#4 | content_lock-ief_integration-2632632-4-D7.patch | 8.39 KB | alberto56 |
Comments
Comment #2
amcgowanca CreditAttribution: amcgowanca at Appnovation commentedComment #3
alberto56 CreditAttribution: alberto56 at Dcycle commentedin your patch, content_lock_inline_entity_form_form_alter() calls _content_lock_is_lockable_node() with a node which is not guaranteed to have a nid, which can cause an undefined unless you have added the patch #2682781: In content_lock_content_lock_node_lockable(), do not assume the node has a nid (PHP Undefined property: stdClass::$nid in content_lock.module on line 984).
Comment #4
alberto56 CreditAttribution: alberto56 at Dcycle commentedNice patch, here is a new version with a few changes:
(1) the patch adds ./content_lock/modules/content_lock_inline_entity_form to ./content_lock, so we end up with ./content_lock/content_lock/modules/content_lock_inline_entity_form if we apply the patch
(2) I think version information is added by the Drupal packaging system, so it should not be added to new modules in a project.
(3) As stated in the previous comment, until #2682781: In content_lock_content_lock_node_lockable(), do not assume the node has a nid (PHP Undefined property: stdClass::$nid in content_lock.module on line 984) makes it in, we need to avoid calling _content_lock_is_lockable_node() with a node which does not have a nid.
Comment #5
pandaski CreditAttribution: pandaski at XiNG Digital commentedComment #6
pandaski CreditAttribution: pandaski at XiNG Digital commentedHappy to see it in next release
Comment #7
DamienMcKennaComment #8
DamienMcKennaPlease try to remember to set the issue status to "needs review" when you upload a patch. Thanks.