On our project that's built on Lightning, we had to use the patch in #2653574-69: Unable to keep nested IEF data separate with multivalue fields. in order to fix the bug where nested IEF forms broke IEF's behavior.
I'm fairly certain that patch (or something architecturally similar) will make it into the next release of IEF... hopefully. If it does, it looks like it will break Lightning's schedulePublication()
Behat step definition inside lightning.behat.inc
.
I have a patch that fixes the to-be-broken test, and will attach it in this issue. For our project, in order to not require a patched Lightning instance, we're actually using a copied-but-modified custom Behat step definition until things are fixed upstream (better than relying on multiple patches to test core functionality).
Comment | File | Size | Author |
---|---|---|---|
#2 | 2846867-2-ief-scheduled-update-fix.patch | 1.17 KB | geerlingguy |
Comments
Comment #2
geerlingguy CreditAttribution: geerlingguy at Midwestern Mac, LLC commentedComment #3
geerlingguy CreditAttribution: geerlingguy at Midwestern Mac, LLC commentedLeaving postponed since #2653574: Unable to keep nested IEF data separate with multivalue fields. is not merged upstream.
Comment #4
phenaproximaThe upstream patch is RTBC, so we could bring it into Lightning now. I'm RTBCing this on the assumption that it will pass our functional tests on Travis CI (which we'll verify before we merge it).
Comment #5
phenaproximaLightning no longer uses Scheduled Updates, and it will be removed as a dependency in #2927527: Remove unused/deprecated modules from codebase. So I'm closing this as outdated.