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.
If I go to module JQuery Update settings and set JQuery for site to 1.7, and next try to add an Action of any type and choose one from the select list the wheel spins for a bit then nothings happens. Trying a second time to choose from the select list does not produce the spinning wheel.
If I turn off jQuery Update or set JQuery version for administrative pages to 1.5 or default (it possible with dev version of JQuery) all working normal.
But exist many modules which doesn't working at all without JQuery 1.7 at least. Sample is fancybox https://www.drupal.org/project/fancybox
Comment | File | Size | Author |
---|---|---|---|
#147 | Screen Shot 2016-02-08 at 9.09.17 AM.png | 100.05 KB | goelmk |
#120 | Screen Shot 2014-12-03 at 12.21.59.png | 53.34 KB | ndf |
#37 | rules-jquery_update_compatibility-1810656-37.patch | 1.67 KB | moonray |
#11 | rules-1810656-11-do-not-test.patch | 1.04 KB | pjcdawkins |
#7 | jquery_update_breaks_rules.PNG | 7.79 KB | deggertsen |
Comments
Comment #1
sylus CreditAttribution: sylus commentedCan confirm the same problem is this to with the .attr() problem with newer versions of jquery?
Comment #2
bonobo CreditAttribution: bonobo commentedI can confirm that this is also an issue with the 2.3 branch of Rules.
However, unlike the jQuery Update conflicts that occurred with both the Features UI and the Views UI (which could be mitigated by selecting a different version of jQuery), the Rules UI is broken with jQuery version 1.5, 1.7, and 1.8, which makes this module pretty unusable in a site running the jQuery Update module.
Despite what is reported in #1792524: code error which causes adding new condition to not do anything when user clicks on "Continue" green button this does not appear to be affected by UUID.
To recreate the issue, install Rules and jQuery Update.
Then, attempt to add any event, condition, or action that requires any of the data selectors. The data selectors do not work.
Comment #3
OnkelTem CreditAttribution: OnkelTem commentedAny solutions?
Comment #4
bonobo CreditAttribution: bonobo commentedOur solution was to not use Rules.
Comment #5
OnkelTem CreditAttribution: OnkelTem commentedBump
Comment #6
ptmkenny CreditAttribution: ptmkenny commentedMarked http://drupal.org/node/1946162 as duplicate of this issue
Comment #7
deggertsen CreditAttribution: deggertsen commentedNo progress on this? I've attached a screenshot just for fun...
Does anybody have any idea where to start? I might try to fix this. I have to have both rules and jquery update so yeah...
Comment #8
Mark TrappFor those wanting to roll back, jQuery Update commit baff5d1 is the last one that works with Rules. Data selectors, but not the initial drop-down menu for actions, works with jQuery Update commit 469fac0.
Comment #9
deggertsen CreditAttribution: deggertsen commentedHere's what I'm getting in the console output in Chrome:
And here's what I get in Firefox:
Does this help anyone? I don't understand javascript and jquery very well so it's Greek to me.
Comment #10
fagoRelated: #1410978: After jQuery Update: Cannot set property '_renderItem' of undefined (rules.autocomplete.js:108)
Comment #11
pjcdawkins CreditAttribution: pjcdawkins commentedI've marked the above mentioned issue (#1410978) as a duplicate of this one.
We could do with more debugging.
jQuery 1.8 is working OK with Rules for me, AFAICS, needing just a couple of tweaks for supporting jQuery UI >=1.10.
Here's the last patch I posted in that thread. It only applies for those running jQuery UI >=1.10. I suppose what we should do is make this patch work with or without, so it's backward/forward compatible.
See http://jqueryui.com/upgrade-guide/1.10/
Comment #12
pjcdawkins CreditAttribution: pjcdawkins commentedPatches are against -dev of course.
Comment #13
Punk_UnDeaDajax detect jquery version right, but not correct jquery ui version
must be like this
please, test it
http://yadi.sk/d/j7Fjkm4O6Ubix
Comment #14
mattsmith3 CreditAttribution: mattsmith3 commented@ Punk_UnDeaD
I was thinking of a similar approach, but with an entry to the variables table.
Check out what jquery_update does now:
... seems to me that all that is missing is jquery_update_jquery_ui_version
Modules could then do a simple variable_get and an if statement to check for compatibility.
Comment #15
mattsmith3 CreditAttribution: mattsmith3 commentedBringing to the jquery_update queue.
https://drupal.org/node/2034987
Comment #16
fubhy CreditAttribution: fubhy commentedDo the older jQuery versions already write into date-ui-autocomplete? Because if they don't, then these changes break backwards compatibility.
Comment #17
pjcdawkins CreditAttribution: pjcdawkins commented@fubhy, I don't think so, but that could be solved by something like this
Comment #18
fubhy CreditAttribution: fubhy commentedYep, that looks better.
Comment #19
fagoThanks - #17 looks good, any testers?
Comment #20
Mark TrappSeems to only work when the admin jQuery is set to 1.5, 1.7, or "use the default" and when the default jQuery is set to 1.5 (which would unfortunately defeat the purpose of using jQuery Update).
With jQuery Update latest head, Rules latest head, and the patch in #17 applied:
Admin set to 1.8
Admin set to 1.7
Admin set to 1.5
Admin set to "use default"
Comment #21
pjcdawkins CreditAttribution: pjcdawkins commentedCurrently on the move so can't test but that surprises me as it works for me on a site with 1.8. Any JS console errors you can paste?
Comment #22
deggertsen CreditAttribution: deggertsen commentedApplied the patch with the following results.
Default is set to 1.7 for everything below
Admin use default: Same results as #20
Admin 1.5: Everything works as expected so far! Thank you!
Admin 1.7: Same results as #20
Admin 1.8: Same results as #20
Comment #23
deggertsen CreditAttribution: deggertsen commentedThis is what shows up in the console when I have admin set to 1.8:
Comment #24
Mark TrappError when data selector has button, but doesn't autocomplete (Admin 1.8/Default All; Admin 1.7, Use default/Default 1.7, 1.8):
Error when add action drop-down menu doesn't work (Admin 1.8/Default 1.5, 1.7):
[Error] TypeError: 'undefined' is not a function (evaluating '$('form.user-info-from-cookie').once') (undefined, line 65)
Error when data selector doesn't render (Admin 1.5/Default 1.7, 1.8):
[Error] TypeError: 'undefined' is not a function (evaluating 'this.element.prop( "disabled" )') (action, line 63)
Comment #25
pjcdawkins CreditAttribution: pjcdawkins commentedThanks. I've made some changes. Seems to have UI issues (the new jQuery UI Menu component has weird gaps between options, and keyboard access seems a bit broken), but I haven't had console errors which is an improvement.
Comment #26
Mark TrappAwesome, it's getting there. Here are my results from the patch in #25:
Admin set to 1.8
Admin set to 1.7
Admin set to 1.5
Admin set to "use default"
Comment #27
OnkelTem CreditAttribution: OnkelTem commentedI confirm #26 report about 1.8 - data selectors have jumping paddings. Patch from #25.
Comment #28
mortenlinkfactory CreditAttribution: mortenlinkfactory commentedIt doesn't work for me with the versions described in #20:
jQuery Update latest head, Rules latest head, and the patch in #17 applied. I've tried with all versions of jQuery.
Chrome still reports
Uncaught TypeError: Cannot set property '_renderItem' of undefined
I've also uninstalled Search Autocomplete, and it still doesn't work.
Comment #29
mortenlinkfactory CreditAttribution: mortenlinkfactory commentedI found a solution for the problem I encountered, which is not exactly the same as the problems encountered in this thread.
I'm adding it here in case other people have this problem and can't find a proper solution. It can be quite difficult to find the core to the problem, when the error message is the exact same.
My problem is related to apachesolr_autocomplete, and there is a fix here: https://drupal.org/node/1491068
Comment #30
WorldFallz CreditAttribution: WorldFallz commentedThe why on earth would you say this issue is "fixed"? Reverting status.....
Comment #31
aukhan CreditAttribution: aukhan commentedConfirming #29
Yes We are having the same issue and our conflict is also due to the apachesolr_autocomplete module ... this modules extends the jQuery autocomplete function which in turn conflicts with rules autocomplete functionality
the patch mentioned here https://drupal.org/node/1491068 fixes the issue for us ....
Comment #32
Anonymous (not verified) CreditAttribution: Anonymous commentedI get a completely different error when I try to select "Select the condition to add: Node is of type":
Uncaught TypeError: Cannot read property 'length' of undefined
Patch #25 doesn't solve that problem.
Using jQuery 1.5 for the admin.
Disabling jQuery Update solves the problem. Seems Rules and jQuery just don't work together.
Comment #33
TBarina CreditAttribution: TBarina commentedI'm using:
With jQuery Update set to using CDN (google or microsoft):
Data selector works showing available items. Also autocomplete works.
The only problem is that I cannot make a selection from the items displayed in the combo box because as soon as I mouse the mouse or press an arrow key the popup combo closes.
With jQuery Update set to using CDN (jQuery): autocomplete doesn't work and no combo popup appears.
If I switch back to CDN = none: everything works fine again!
Comment #34
byue CreditAttribution: byue commentedtried #23 and got the following error on chrome:
Uncaught TypeError: Object [object Object] has no method 'menu'
e.widget._create
(anonymous function)
e.Widget._createWidget
e.(anonymous function).(anonymous function)
(anonymous function)
p.extend.each jquery.min.js?v=1.8.2:2
p.fn.p.each jquery.min.js?v=1.8.2:2
e.fn.(anonymous function)
Drupal.rules.autocomplete
(anonymous function)
p.extend.each jquery.min.js?v=1.8.2:2
p.fn.p.each jquery.min.js?v=1.8.2:2
$.fn.once jquery.once.js?v=1.2:55
Drupal.behaviors.rules_autocomplete.attach
(anonymous function) drupal.js?mu5o20:76
p.extend.each jquery.min.js?v=1.8.2:2
Drupal.attachBehaviors drupal.js?mu5o20:74
Drupal.ajax.commands.insert ajax.js?v=7.23:542
Drupal.ajax.success ajax.js?v=7.23:400
ajax.options.success ajax.js?v=7.23:164
c.success jquery.form.min.js?v=2.69:11
k jquery.min.js?v=1.8.2:2
l.fireWith jquery.min.js?v=1.8.2:2
y jquery.min.js?v=1.8.2:2
d jquery.min.js?v=1.8.2:2
Comment #35
byue CreditAttribution: byue commentedretried #33, works now thank you
Comment #36
ericduran CreditAttribution: ericduran commented#25 looks good but the menu addition shouldn't be done that way. It seems this is being done because of this bug in jquery_update #2086105: jQuery UI menu not including
I'm going to fix that bug now and instead if the rules.autocomplete depends on jquery autocomplete the menu.js should just be included by the dependency system.
Does this make sense?
Comment #37
moonray CreditAttribution: moonray commentedI rerolled the patch in #25 without the "jQuery UI menu not being included" fix; it's fixed in jQuery Update module, as per #36.
It seems #26 requires some additional tweaks to make this work for more use-cases than mine. This patch solved the issue for me, though.
Comment #38
Anonymous (not verified) CreditAttribution: Anonymous commented-edit- my issue was caused by the clientside validation extension. The patch from #37 works.
Comment #39
Anonymous (not verified) CreditAttribution: Anonymous commentedPatch #37 works for me
Comment #40
Iztok CreditAttribution: Iztok commentedPatch not working on the dev version of jQuery update module.
Comment #41
TBarina CreditAttribution: TBarina commentedI still confirm that #37 doesn't work when using CDN.
Is there any way to fix it?
Comment #42
muschpusch CreditAttribution: muschpusch commentedThe patch works when using 1.5 of jquery update but breaks when using default. So this needs work...
Comment #43
iLLin CreditAttribution: iLLin commentedPatch #37 works for me with version 1.10. In the data selectors it was spitting out the html markup and throwing the
Cannot set property '_renderItem' of undefined
error and that is now fixed.Comment #44
dmsmidtPatch is not solving anything for me.
But I get the error even without JQuery update.
Latest Rules dev version
JQuery update 7.x-2.3
Comment #45
joco_sp CreditAttribution: joco_sp commentedI disabled and deleted the JQuery update, but the problem is still there.
Comment #46
myselfhimself CreditAttribution: myselfhimself commentedPatching Rules module with #37 along with installed jquery_update 7.x-2.3+15-dev (jQuery 1.10) makes Rules Add action form's JS rework!
Thanks!
Comment #47
ifrikUsing
The drop-down to use a condition works, but the Data selector field does not have autocomplete and the Data Selector list isn't a collapsed list, but just a word.
However after clicking on 'Save' without filling in a value for the data, I get the expected error message - and the autocomplete works and Data selector link is the collapsed table that it should be.
Comment #48
dobe CreditAttribution: dobe commented#37 patch appears to work for me so far with the latest dev version of jQuery update
Comment #49
himanshupathak3 CreditAttribution: himanshupathak3 commentedHello,
No need for any patch, if you have installed jquery update select version 1.7 also do not select any cdn (google), for cdn choose none, Problem is resolved. :)
Thanks,
Himanshu
Comment #50
xcel CreditAttribution: xcel commentedAgree to #33 and 49.
Thanks !
But if you need CDN ... maybe you could disable it while u need to edit rules (at least you are not stuck during development)
Comment #51
rei CreditAttribution: rei commentedconfirm patch #37 works with jquery_update 7.x-2.3+15-dev (jquery 1.10) and rules 7.x-2.6
Comment #52
aether CreditAttribution: aether commentedYes. #37 works.
rules-7.x-2.6
jquery_update-7.x-2.3+15-dev
Comment #53
AnybodyI can NOT confirm #49! I've selected jQuery 1.7 for admin and the normal theme and the error is still there even after clearing caches.
First after applying patch #37 and clearing caches everything worked again.
I think we should move this forward and set it RTBC soon or do further investigations. It's major.
Comment #54
tregismoreira CreditAttribution: tregismoreira commentedI'm using:
- Drupal 7.26
- jQuery Update 7.x-2.3+17-dev
- Rules 2.6
So:
- #37 patch works for me! Thanks a lot!
- #49 doesn't work :/
Comment #55
ginogarcia CreditAttribution: ginogarcia commentedHi guys, I am pretty new to Drupal and programming in general, so pleas bear with me... I got the data selector working by configuring the jQuery_update module:
Default JQuery Version: 1.7
Alternate JQuery Version: 1.7
JQuery Compression Level: Development (I doubt this should make any differences)
JQuery and JQuery UI CDN : JQuery
Hope this help!
Gino
Comment #56
mouhammed CreditAttribution: mouhammed commentedThe #55 work for me.
I think that its the JQuery UI CDN none value doesn't work.
Thanks for @ginogarcia.
Comment #57
joep.hendrix CreditAttribution: joep.hendrix commentedVery strange: #55 works for me too.
Local or via Google cdn does not work.
Comment #58
hockey2112 CreditAttribution: hockey2112 commented#55 worked for me as well. I am using Jquery Update 7.x-2.4. Thanks!
Comment #59
Tritof CreditAttribution: Tritof commented#55 works for me too. Jquery update version = 7.x-2.4.
Thanks very much !
Comment #60
dobe CreditAttribution: dobe commentedProblem with #55 off the top of my head is your Views UI is now probably broken... Among other administrative things. The patch (#37) must be applied to fix the issue. Yes there are many ways of avoiding the issue only to be slapped by another.
Comment #61
GoddamnNoise CreditAttribution: GoddamnNoise commentedUsing:
- Drupal 7.27
- Rules 7.x-2.6
- JQuery Update 7.x-2.4 (Default JQuery Version: 1.8, Alternate JQuery for administrative pages: 1.5, CDN: none)
And applying #37 patch.
Problem still there: add action drop-down works; data selector renders as plain text field: no button, no autocomplete (image attached). Looking at the Chrome javascript console, i got this error:
Solution suggested in #47 seems to work (leaving the data selector empty and clicking the "Continue" button shows the expected error, but everything begins to work as it should: data selector appears, button works, autocomplete works and so on).
Using the jQuery CDN seems to solve the problem too (but many things stop to work then on my frontend, so i can't do this).
Comment #62
GoddamnNoise CreditAttribution: GoddamnNoise commentedComment #63
GoddamnNoise CreditAttribution: GoddamnNoise commentedComment #64
ofry CreditAttribution: ofry commentedAs temporary solution, you can use different JQuery versions in front-end and back-end of your site (last dev version of jquery_update can help you with it).
Comment #65
GoddamnNoise CreditAttribution: GoddamnNoise commentedThat's what i've done and what i've explained in #61, but it doesn't work even if i use different JQuery versions in front-end and back-end. The only things that have worked for me are those explained in #61.
Comment #66
mctwist CreditAttribution: mctwist commented#55 worked for me. Thanks! The only thing thing that changed from when it was last working (yesterday morning) was upgrading to the newest version of Drupal (yesterday afternoon).
Comment #67
DrCord CreditAttribution: DrCord commentedThe patch in #37 worked perfect for me. I was getting HTML code in the data selector. I am using jQuery 1.8 via jQuery Update.
Comment #68
xandeadx CreditAttribution: xandeadx commentedI use last dev jQuery update and use default drupal jQuery version on admin paths. And it's work.
Comment #69
heddnUsing this on a commerce kickstart site and bootstrap theme that uses jquery 1.8. Switching to use jquery 1.7 on the admin side fixed the issue. Marking as fixed as this combination seems to resolve the issue for many folks.
Comment #70
GoddamnNoise CreditAttribution: GoddamnNoise commentedJQuery 1.7 breaks Rules UI as explained in #2
Comment #71
quwat CreditAttribution: quwat commentedI updated the Jquery to the dev version. Rules starting working like a charm.
Comment #72
i.bajrai CreditAttribution: i.bajrai commentedI can confirm #55 is working
Comment #73
greenwork CreditAttribution: greenwork commentedI downgraded to 1.5 and everything on commerce kickstarter is working again. I am using the google CDN
Comment #74
markus_petrux CreditAttribution: markus_petrux commentedMarking the issue as fixed would need some kind of action. Maybe making rules work with any version of jQuery, documenting the dependency..., which is not a nice solution because it may conflict with other modules.
Comment #75
geek-merlin* tested #37 and it worksforme
* based on the about 10 other confirmations setting rtbc, based on considerations:
** #37 is already a huge win
** if there are or will be some jquery versions that break this should be a followup
** problems with CDN (which are also mentioned) are not a needswork for this patch but must be addressed separately, see #982188: Work around Same-Origin Policy: Cross-Origin Resource Sharing (CORS) support
APPENDIX: here are my CDN exclusion settings:
*/rules.autocomplete.js
*/jquery.ui.widget.min.js
*/jquery.ui.button.min.js
*/jquery.ui.core.min.js
*/jquery.ui.menu.min.js
*/jquery.ui.autocomplete.min.js
Also created #2275505: Provide reasonable jquery-ui blacklist
EDIT: #55 is a workaround, NOT a patch.
Comment #76
gintass CreditAttribution: gintass commented#55 is working. I wish this problem would be mentioned on the main project page. It could save a lot of time to other people.
Comment #77
Anonymous (not verified) CreditAttribution: Anonymous commentedAgree #37 works. Thx for this patch
Comment #78
tripper54 CreditAttribution: tripper54 commentedComment #79
Train CreditAttribution: Train commentedI would like to mention that when using #55 and behind https://, the jQuery and Microsoft CDNs will not load over https://. Google is fine.
Sorry, jQuery Update 7.x-2.4, Rules 7.x-2.7...
Comment #80
cknoebel CreditAttribution: cknoebel commented#55 works for me however my combo of stuff is slightly different:
* Default version: 1.10
* Alternate version: 1.5
* Compression: minified
* CDN: Google
The other CDNs didn't work for me and alternate versions over 1.5 didn't work either. Also, the patch in #37 did not work for me.
Comment #81
lmeurs CreditAttribution: lmeurs commentedThanks for #37!
Patch solved my JS error when adding a "Set a data value" action (with Rules 7.x-2.7, jQuery Update 7.x-2.4).
Comment #82
slucero#37 fixed the issue perfectly for me too!
* Rules 7.x-2.7
* jQuery Update 7.x-2.4
Comment #83
cdmo CreditAttribution: cdmo commentedI found using 1.7 with either no CDN or jQuery worked for me.
jQuery Update 7.x-2.4
Rules 7.x-2.7
Comment #84
joshua.boltz CreditAttribution: joshua.boltz commentedHello,
I first stumbled upon this issue after installing and trying out the bootstrap_tour module.
Depending on the jquery_update settings, that module will not work. It especially conflicts with Menu Block.
So, in order to get the tour module working, I had to set jquery_update to 1.7, but then that broke mini panels and rules ui, because they work best with 1.5.
So, the only way I can get Rules UI data selectors to work is set jquery_update "Default jQuery Version" to 1.7 and "Alternate jQuery version for administrative pages" to 1.5, so tour and other admin-related modules/functionality can still work.
Rules 7.x-2.7
jQuery Update 7.x-2.4
Panels/Mini-Panels 7.x-3.4
Ctools 7.x-1.4
Menu Block 7.x-2.4
I'm sure I'll stumble upon another instance where something doesn't work, so I am interested in any ideas to hopefully get everything working using the same jQuery version.
Comment #85
2pha@joshua.boltz : Using the dev version of jquery update now allows you to use the default drupal jquery for admin pages. Give it a go.
Comment #86
hansfn CreditAttribution: hansfn commentedPatch #37 works for me - even using jQuery Update with jQuery 1.8. It's the same patch used by other projects. Any reason this wasn't included in Rules 2.7?
Comment #87
joelstein CreditAttribution: joelstein commentedPatch #37 works for me!
Comment #88
paean99 CreditAttribution: paean99 commented#37 seems to works for me.
Open Atrium 2.21, jQuery Update 2.4, Rules 2.7.
Thanks.
Comment #89
deggertsen CreditAttribution: deggertsen commentedThe day this gets committed will be a good day. =)
Comment #90
caponey CreditAttribution: caponey commentedwould it be possible to disable JQuery Update while we configure our Rules? Then enable it when we're finished, or will JQU completely make the Rules not work either
Comment #91
2pha@caponey The latest dev version of Jquery Update allows you to specify the default jquery for the admin pages, effectively disabling it.
Comment #92
rv0 CreditAttribution: rv0 commentedGot burned with this too today.
We need 1.7 for some fancy admin pages in the backend
+1 for getting #37 committed
Comment #93
joelpittetThe patch in #37 looks very similar to how we fixed coffee over here #1864550: Coffee fails with jquery_update 7.x-2.3+ (2.x-dev) installed.
Though we did a version detect for 1.10
Comment #94
rosell.dk CreditAttribution: rosell.dk commentedPatch #37 works for us as well. +2 for getting it committed (+1 from me, and +1 from my customer ;)
Comment #95
avinash_raut CreditAttribution: avinash_raut commentedPatch is not working for me..
But if you are working in commerce kick start with drupal then just you can solve this problem simply doing five change into it.
Five Key to fix this problem..
1. Download Module Jquery_update and enable it from drupal module.
2. Modify .live to .on in .../profile/commerce_kickstart\libraries\colorbox\jquery.colorbox.min.js (line no. 543)
3. Modify .live to .on in .../profile/commerce_kickstart/modules/commerce_kickstart/commerce_kickstart_search/commerce_kickstart_search.js (line no. 7)
4. Modify .live to .on in .../profile/commerce_kickstart/modules/contrib/commerce_add_to_cart_confirmation/js/commerce_add_to_cart_confirmation.js ( line no. 9)
5. Modify .live to .on in .../profile/commerce_kickstart/modules/contrib/commerce_hosted_pci/js/commerce_hosted_pci.js ( line no. 32)
clear cache and try.
Comment #96
Leeteq CreditAttribution: Leeteq commentedWith so many confirmations, isnt it time to commit #37 to -dev?
Comment #97
Argus CreditAttribution: Argus commentedyep, but this is the real issue: https://www.drupal.org/project/issues/rules?text=&status=8&priorities=Al...
Comment #98
chrisfromredfinArgus - what is the real issue? That link is to a queue. Also, #37 seems to work for me. :)
Comment #99
Argus CreditAttribution: Argus commented@cwells ignor that, was refering to the huge amount of issues for Rules that have status "need review"! Also https://www.drupal.org/project/issues/rules?status=14 issues that have status Reviewed & tested by the community
Comment #100
cmonkedo CreditAttribution: cmonkedo commented#37 worked for me.
Comment #101
jordan8037310 CreditAttribution: jordan8037310 commentedTried patch #37 but no juice.
Implemented the alternative administrative jQuery as 1.5 instead of site's jQuery 1.7. This solved my issues.
Comment #102
jordan8037310 CreditAttribution: jordan8037310 commented//doublepost, sorry
Comment #103
ofry CreditAttribution: ofry commentedjordan8037310, can you give me examples of "no juice"? For sample, try to install Firefox with Firebug extension and give me information from Firebug console.
Comment #104
ofry CreditAttribution: ofry commentedComment #105
Joe HuggansI can confirm that this works if you set
jQuery and jQuery UI CDN = jQuery
No need to apply patch in my case
Comment #106
peterjlord CreditAttribution: peterjlord commented@joeuk Thanks! worked for me as well on Version 1.7 and 1.5 for admin
Comment #107
ofry CreditAttribution: ofry commentedBut if I set JQuery for admin below than 1.7, I can't use FancyBox UI https://www.drupal.org/project/fancybox
Comment #108
joelpittet@ofry in the latest dev of jquery_update (maybe even stable) you can set the admin jquery used different from your front end. So unless you are using fancybox on the back end you shouldn't need to worry here.
I use fancybox as well.
Comment #109
ofry CreditAttribution: ofry commentedjoelpittet, no. If I set JQuery for admin pages to 1.5 or default, even if I set to front-end version 1.7+, I can't edit settings of Fancybox module. Because it checks back-end version of JQuery before show settings form.
Comment #110
joelpittet@ofry oh sorry didn't know that. I'm running 1.7 on both front and back, it's been the best balance so far. I'm running with patch #37
Comment #111
geek-merlin#104:
> I can confirm that this works if you set
> jQuery and jQuery UI CDN = jQuery
HUH, this is strange stuff. I dug the source a bit:
* due to bug #2268035: no case for jquery option as CDN in jquery_update_jqueryui_replace, this reset jquery version to core 1.4.4 but was the only way to do so
* but now this is fixed: #1548028: Make the default jQuery version (1.4.4) for D7 an option
so the right way to do that:
* use the dev version of jquery_update
* and select "Default (provided by drupal)" as admin ui version.
Comment #112
agileadamThis combo worked for me:
- Patch #37
- Rules 7.x-2.7
- jQuery Update 7.x-2.4
- jQuery 1.8 frontend
- jQuery 1.7 admin (1.8 caused autocomplete to load at top left of screen)
- jQuery and jQuery UI CDN: jQuery
Comment #113
rosell.dk CreditAttribution: rosell.dk commented@axel.rutz: Ok, thanks for the research, and the explanation why setting jquery as CDN strangely "fixes" our problem. Still, it would be preferable that Rules just works - with any version of jQuery. Patch #37 seems to be the fix, while changing settings in jQuery Update is a workaround. Also consider, that if Rules forces users of jQuery Update to set it up, so it uses the dated version of jQuery that is in core, it means that the Rules module actually requires jQuery Update to be set up to do nothing (for admin ui). While it may be that many only need a newer version of jQuery for the frontend, most people will have it set to a new version on the admin ui as well (being that "Default (provided by drupal)" is a new setting in jQuery Update) - so implementing patch #37 in the next release will spare many people the agony of Rules strangely not working and the trouble of finding the workaround. And don't forget that some do need jQuery update on the admin ui as well. At least I did.
Comment #114
GoddamnNoise CreditAttribution: GoddamnNoise commentedTotally agree with #113
Comment #115
sch2 CreditAttribution: sch2 commentedPatch #37 worked for me, thanks.
Comment #116
ofry CreditAttribution: ofry commentedComment #117
ndf CreditAttribution: ndf commentedIt's fixed with jquery_update-7.x-2.x (current dev) and rules-7.x-2.7 (current stable).
So its fixed in jquery_update not in rules.
see: https://www.drupal.org/node/2235771#comment-9298411
Comment #118
ofry CreditAttribution: ofry commentedIf I do so, I can't use FancyBox UI. https://www.drupal.org/node/1810656#comment-9197591
Comment #119
danylevskyinielsdefeyter, still not working with jquery_update-7.x-2.x (current dev) and rules-7.x-2.7 (current stable).
Comment #120
ndf CreditAttribution: ndf commentedHi Danylevskyi,
This are my (working) version options at /admin/config/development/jquery_update
> Default jQuery version: "1.7"
> Alternate jQuery version for administrativ pages: "Default (provided by Drupal)"
jquery_update-7.x-2.4+5-dev
rules-7.x-2.7
Does that help you?
Comment #121
dmsmidtUsing "Default (provided by Drupal)" works for me as well.
This is also usefull for other modules admin interfaces (like: path_breadcrumbs).
Comment #122
ofry CreditAttribution: ofry commentedsee comment #109
Comment #123
dmsmidt#109 is no rules issue, please add a new issue to the fancybox issue queue
Comment #124
ofry CreditAttribution: ofry commentedReally? It's rules UI issue because it's NOT working if JQuery > 1.5. And patch ALREADY done and tested many times! Why not commit it???
Comment #125
MrAdamJohn CreditAttribution: MrAdamJohn commented@ofry I think it is actually not a newer version of jquery, rather, use of the jquery_update module that allows a different version (an updated one, presumably) to be used for different parts of a site.
There are people using Rules with the newer versions of JQuery without any problems.
This issue queue has what is the best summary of the specifics of this issue as I've seen it.
Simply disabling jquery_update module (if possible) will mitigate the symptoms and verify the issue on your site.
As I see it these issues are related... but if there is another problem hopefully someone will chime in.
Cheers!
Comment #126
ofry CreditAttribution: ofry commentedTry to reproduce this: set JQuery version for admin pages to 1.5. Rules UI will work! But FancyBox UI will NOT work, because it checking JQuery version before show me UI :(
So it's Rules bug (if it doesn't working with JQuery for administrative pages = 1.7)
Comment #127
andypostPlease update issue summary and add steps to reproduce
Comment #128
ofry CreditAttribution: ofry commentedComment #129
dobe CreditAttribution: dobe commentedI have been following this issue for a long time. The issue is Rules interface breaks when using JQuery 1.7+. It is very simple. Enable jQuery 1.7+ on admin pages using jquery update (after all you configure Rules in admin pages). Now go and administer rules. What is that? Oh not working (Selectors are now broken)... Apply patch... It works (Selectors are now functioning).
If you can do those steps and your Rules pages don't end up broken then there is a different issue here. As of right now however, this thread is blistered with a whole bunch of ways to "avoid" it, not one of them saying that is working fine without the patch. The only things that has fixed it is the patch #37.
Please RTBC #37.
Comment #130
aasarava CreditAttribution: aasarava commentedAre we sure it's not the overlay that's causing the problem? Stepping jquery update down to "default" doesn't fix the issue, but editing a rule without the overlay fixes the problem for me. Does this work for anyone else?
Comment #131
ofry CreditAttribution: ofry commentedaasarava, yes, I'm sure. You can make sure too, if you install Firefox and Firebug extension for Firefox. Next enable Firebug on rule page and go to "Console" tab. You will see some Javascript errors. And these errors fixed in patch #37.
Comment #132
Leeteq CreditAttribution: Leeteq commentedIt is puzzling that an issue of this nature and between two such important modules keeps lingering among the open issues for so long.
An alternative approach might be a new configurable setting in Rules where we can enforce a specific JQuery version only on Rules pages? Would that help work around similar situations in the future?
Comment #133
ron_s CreditAttribution: ron_s commentedWe don't use the overlay, and had data selector UI issues with Rules 7.x-2.7 and jQuery Update 7.x-2.4. These issues occurred with our jQuery version set to 1.8. Applying patch #37 resolved the problem.
Comment #134
gagarine CreditAttribution: gagarine commentedPatch #37 is working with jQuery Update with "version for administrative pages" set to 1.7, 1.8 and 10.0 but not for 1.5. I don't think it's a problem and encourage maintainer to commit this.
I didn't test the patched without jQuery Update. Anyone did?
Comment #135
ofry CreditAttribution: ofry commentedHm... I'm see patched Rules UI working for "Default (provided by Drupal)", "1.5" (works same as default JQuery default), "1.7" (data selector opens fine, click on the button works, BUT if I click on autocomplete string, then it normally inserted in textfield. But autocomplete tab closes and does not reopen until I click autocomplete button again).
Maybe, it's JQuery UI 1.10.2 problem.
Comment #136
blacklabel_tom CreditAttribution: blacklabel_tom commentedBump! this is working for me, can this be rolled in please?
Comment #137
Argus CreditAttribution: Argus commentedNo need to bump because it won't work. See #97-99.
Comment #139
fagoThanks all for testing - looks like #37 is solid. I fixed the comments to be less than 80chars and committed #37.
Comment #141
jagadmarx CreditAttribution: jagadmarx commented#55 worked for me.
Comment #142
DrCord CreditAttribution: DrCord commented@Argus - does that mean that no new patches or updates are going to be applied to rules?
Comment #143
Argus CreditAttribution: Argus commented@DrCord: No, I just want to point out there are a lot issues for Rules that have the status "Reviewed and tested by the community", and obviously limmited time by the maintainers. Good this one got commited... :-)
Comment #144
doppel CreditAttribution: doppel commented#37 works for me. Thanks.
Comment #145
agerson CreditAttribution: agerson commentedI am experiencing this issue again. When JQuery is set to 1.5 all works well. When I change it to 1.7 the rules data selector js does not work. I update both Rules and JQuery Update to the latest prod versions.
Comment #146
heddnre #145: It is almost always better to open a follow-up issue, rather than re-open an old issue. You can always cross-post and link them. Moving back to fixed.
Comment #147
goelmk CreditAttribution: goelmk commentedWhen I'm trying edit any rules, there are no links available for "Add Event, "Add Condition" and "Add Action". Tried downgrading jQuery version to 1.5 and even 1.4 but no success. Any help in this regard will be much appreciated.
Thanks in advance!
Comment #148
goelmk CreditAttribution: goelmk commentedComment #149
chellman CreditAttribution: chellman as a volunteer commentedgoelmk, please post a new support issue for this. When you do, please provide more information, like any errors or warnings you see in your browser's JavaScript console, what version of Drupal you're running, and so on.
Comment #150
rsvelko CreditAttribution: rsvelko as a volunteer commentedFor those who still have problems with the Data Selector not working:
See https://www.drupal.org/node/1675668#comment-6272178:
"
zhangtaihao commented 5 years ago
For anyone who comes across this issue, I have also encountered a similar problem when using "Production" jQuery from Google CDN (in Performance settings). The "solution" is to not use a CDN.
Weird...
"
So go into jquery_update's settings and disable CDN usage - set to None.
See #2879032: problems when using a CDN to load jquery and jquery_ui
Comment #151
maxplus CreditAttribution: maxplus commentedThanks,
#150 is working for me
Comment #152
tonytheferg CreditAttribution: tonytheferg commentedSo I am still experiencing this, and setting CDN to none did work, but I don't know what the ramifications of that are?
Also, if you just save the page with nothing in the selector, the dropdown will return.. Kinda hacky, not sure which would be best.
Comment #153
Dimetry CreditAttribution: Dimetry commentedThanks for the information.