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.
jQuery UI 1.10 was committed in #1175830: Update to jQuery UI 1.10.2.
Problem explained in comments #112–#114. Upstream Create.js issue: https://github.com/bergie/create/issues/173.
Comment | File | Size | Author |
---|---|---|---|
#7 | Screenshot_4_5_13_11_53_AM.png | 115.51 KB | jessebeach |
#6 | Screen_Shot_2013-04-05_at_11.48.02_AM.png | 395.16 KB | jessebeach |
#5 | Screenshot_4_5_13_11_44_AM.png | 257.18 KB | jessebeach |
#3 | create_js_jquery_ui_1_10-1960612-3.patch | 7.51 KB | Wim Leers |
#3 | interdiff.txt | 2.86 KB | Wim Leers |
Comments
Comment #1
Wim LeersComment #2
Wim LeersDetails on debugging & brokenness at https://github.com/bergie/create/issues/173#issuecomment-15867333.
Comment #3
Wim LeersGot everything working again based on feedback from bergie.
Comment #4
Wim LeersA straight backport of #3 to D7 Edit was confirmed working: #1962274-4: jQuery UI 1.10 compatibility.
Can we please get this reviewed & committed ASAP, so that Edit works again in D8? Thanks.
Comment #5
jessebeach CreditAttribution: jessebeach commentedI get a JS error when quick editing a node (simple Article from the front page view listing)
Comment #6
jessebeach CreditAttribution: jessebeach commentedGoing through the stack, we're finding the predicate element (the body field) correctly.
Comment #7
jessebeach CreditAttribution: jessebeach commentedThe call to this function
seems to be failing. It's in file create-editonly.js around line 600.
Comment #8
jessebeach CreditAttribution: jessebeach commentedHmmm, and now it appears to be working. Maybe I just had a cached version of the JS file. Sigh.
Comment #9
jessebeach CreditAttribution: jessebeach commentedI'm getting an AJAX error when attempting to save a body field from Quick edit.
Comment #10
Wim LeersI'm working with Jesse on figuring out #9, but I can't reproduce it locally, nor on simplytest.me, nor can she on a fresh install. It looks like it was something on her system.
Comment #11
jessebeach CreditAttribution: jessebeach commentedSo, Wim and I verified that the AJAX error I'm seeing is not present on simplytest.me. I'm investigating my local setup further, but it seems that the errors I'm getting have to do with my local setup and not this patch.
Comment #12
jessebeach CreditAttribution: jessebeach commentedNah nah nah, not so fast. I looked into my local error further and found that when the language module is enabled, I get the error in #9 when saving an in-place edited field.
The trigger for this error may be something we stumbled upon with this patch instead of introduced. The ultimate cause is still unknown. From my attempts to debug, I can't get a breakpoint to catch in the functions mentioned in the error. The error feels like a red herring.
Comment #13
Wim Leers1) This patch only modifies JavaScript.
2)This patch cannot have changed the data that gets sent to the server.
Hence you've discovered a bug that must already have existed before this patch. Please open a new issue for it (or I will). We should go back to the commit before jQuery UI 1.10 and there it should occur as well.
Comment #14
jessebeach CreditAttribution: jessebeach commentedAgreed with #14. I'm putting together the findings from my debugging of the AJAX issue and opening a new ticket. I'll link it here. What this patch here does is expose what has been dormant in the field code before now.
Comment #15
jessebeach CreditAttribution: jessebeach commentedHere's the related bug #1963334: Edit incompatible with language module (?): AJAX save of an Article node results in an error related to the image field.
Comment #16
webchickHm. That's sub-optimal, but it'd definitely be good to get this working at all again.
Committed and pushed to 8.x. Thanks.
Incidentally, this makes me cranky:
And especially this:
Midgard is a different CMS project entirely, it doesn't really make sense to pull their namespace into our project. However, it looks like according to https://github.com/bergie/create/issues/173, having that string hard-coded to "Midgard" is this is an upstream issue, hopefully will be resolved with a subsequent Create.js update.
Comment #17
Wim LeersRE: "incidentally": It's "just" jQuery UI Widgets namespacing working in very very unexpected ways. It annoys the hell out of me too.
(The Drupal 8 equivalent would be: "plugins for Drupal 8 only work if you declare them in the 'Drupal' namespace".)
Comment #18
Wim LeersThanks for the follow-up issue, Jesse! I assigned it to myself to ensure I investigate it further.