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.Problem/Motivation
This issue is postponed on #2152073: Bump Drupal core's PHP requirement to 5.4.2.
It is spun off from #2075185: When an entity is in-place edited (i.e. saved), other instances of that entity on the same page are not updated (no propagation).
A hack to support PHP 5.3 must be undone once PHP 5.4 is the minimum requirement for Drupal 8.
Proposed resolution
The solution to this issue is known and will be attached.
User interface changes
None.
API changes
None.
Original report by @jessebeach
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | unravel-edit-hack-2156793-2.patch | 2.29 KB | Wim Leers |
Comments
Comment #1
jessebeach CreditAttribution: jessebeach commentedThis patch unwinds the hack (as noted here: https://drupal.org/files/issues/interdiff_718.txt) put in place by Wim Leers in #2075185-11: When an entity is in-place edited (i.e. saved), other instances of that entity on the same page are not updated (no propagation).
I tested the patch on PHP 5.3.14 and it results in a PHP fatal error. After switching to PHP 5.4.4, the in-place editing works perfectly again.
Comment #2
Wim LeersDrupal 8 requires PHP 5.4 as of last week, so we can now clean this up!
Patch didn't apply anymore; straight reroll.
Comment #3
dawehnerDo we have a meta issue to track all of those issues?
Comment #4
dawehner.
Comment #5
dawehner.
Comment #6
Wim Leers@dawehner: not AFAIK.
Comment #7
webchickCommitted and pushed to 8.x. Thanks!
Comment #8
Wim LeersHurray for getting quick fixes in quickly! :)