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.
This is a very uncommon issue, but if you hacked drupal to include a newer version of jQuery (as I did for public facing pages), then you need to patch the javascript code to replace .attr() with .prop(). See this stackoverflow issue.
It only happens if you have jquery 1.6 or higher.
Comment | File | Size | Author |
---|---|---|---|
#7 | Screen Shot 2013-10-26 at 3.49.58 PM.png | 79.61 KB | stopshinal |
#1 | ajax_comments_jquery_1.6_support-2.patch | 951 bytes | ttkaminski |
ajax_comments_jquery_1.6_support.patch | 1.07 KB | ttkaminski | |
Comments
Comment #1
ttkaminski CreditAttribution: ttkaminski commentedHere's a patch that's easier to apply.
Comment #2
tntclaus CreditAttribution: tntclaus commentedpatch from comment #1 works for me (jquery 1.7)
Comment #3
muschpusch CreditAttribution: muschpusch commentedthis breaks ajax_comments when using default jquery shipped by drupal
Comment #4
Exploratus CreditAttribution: Exploratus commentedWorks for me with 1.7
Comment #5
aromka CreditAttribution: aromka commentedWorks for me with 1.8 as well
Comment #6
muschpusch CreditAttribution: muschpusch commentedDudes! It may even work with jquery 2.0 but it needs to work with the default version drupal ships with too!
Comment #7
stopshinal CreditAttribution: stopshinal commentedUsing jQuery 1.7 I get this AJAX dialogue error when I hit 'reply' on a comment thread.
An AJAX HTTP error occurred.
HTTP Result Code: 404
Debugging information follows.
Path: /ajax_comments/reply/2305/4
StatusText: Not Found
ResponseText:
Page not found | Chicken.io
@import url("http://chicken.dev/modules/system/system.base.css?mvamz6");
Comment #9
kmontyYeah, it seems the dev branch of this module is broken.
Comment #10
kmontyalso see #2078949: Compatibility with jquery update
Comment #11
formatC'vt CreditAttribution: formatC'vt commentedtry latest dev version, please
Comment #12
kmontyVerified this issue was resolved with the previous release.