Hi

Since I have upgraded my site from drupal 7.39 to drupal 7.40 my site has developed several issues.

I'm getting a critical error when using firefox developer tool, here's what Im getting when editing a node:

TypeError: $.cookie is not a function toolbar.js:29:19
TypeError: $.cookie is not a function collapsiblock.js:75:1
Use of getAttributeNode() is deprecated. Use getAttribute() instead. jquery.js:55:0
Password fields present on an insecure (http://) page. This is a security risk that allows user login credentials to be stolen.[Learn More]
Password fields present on an insecure (http://) iframe. This is a security risk that allows user login credentials to be stolen.[Learn More]
Password fields present in a form with an insecure (http://) form action. This is a security risk that allows user login credentials to be stolen.[Learn More]
Use of getAttributeNode() is deprecated. Use getAttribute() instead. jquery.js:55:0
Use of attributes' nodeValue attribute is deprecated. Use value instead. jquery.js:55:0
TypeError: $.cookie is not a function tabledrag.js:164:7

And here's what I'm getting on the blocks page:

Use of getAttributeNode() is deprecated. Use getAttribute() instead. jquery.js:55:0
Use of attributes' nodeValue attribute is deprecated. Use value instead. jquery.js:55:0
TypeError: $.cookie is not a function tabledrag.js:164:7

This is resulting in some strange behavior, problems noticed so far include:

Unable to use drag and drop on the blocks screen (and other areas).
WYSIWYG not showing on edit node.
Galleria not showing galleries for admin, but everyone else inc anonymous can see the galleries.

There's probably a few other things broken too that I have yet to discover.

Originally I thought it was just WYSIWYG misbehaving but it's much worse.

Here's

Any help to solve my issue is greatly appreciated.

Many Thanks

Comments

Babymaggie created an issue. See original summary.

cilefen’s picture

Are you using any jQuery-related modules such as jquery_update?

Babymaggie’s picture

Hi cilefen

Thanks for the reply.

No, not using any jquery related modules or jquery update.

This is so strange as the site was fine until the upgrade.

Any ideas as I would love to get to the bottom of this and restore my site to normal as I'm a little worried now.

Thanks

cilefen’s picture

On the network tab of your browser tools, are you seeing any assets getting 404s, like misc/jquery.cookie.js?

Babymaggie’s picture

Hi, I'm getting a 406 error misc/jquery.cookie.js?v=1.0 with a little red square icon next to it.

cilefen’s picture

This could be a duplicate of #594814: query.cookie.js 'Page Not Found' 406.shtml error or the longer thread in #1052372: Page Not Found - misc/jquery.cookie.js - But it IS There!. Look in those for possible solutions, which seem to center around an Apache security configuration and the workaround if Apache cannot be modified being to enable JS aggregation.

The are normal warnings for the old version of jQuery in core so ignore them or use jquery_update:

Use of getAttributeNode() is deprecated. Use getAttribute() instead. jquery.js:55:0
Use of attributes' nodeValue attribute is deprecated. Use value instead. jquery.js:55:0

Babymaggie’s picture

Thanks for taking the time to help cilefen

Turning on Aggregate JavaScript files in Performance Bandwidth optimization seems to have fixed this.

Can't help wondering why this problem has reared it's ugly head in the last day or so since the upgrade? Any ideas?

The site has been around for a few years now and never come across something quite so disastrous.

I'm so grateful for your assistance as I thought the site was borked!

Many thanks for your time cilefen

cilefen’s picture

Title: Getting a TypeError: $.cookie is not a function since upgrade from 7.39 to 7.40 » 406 HTTP error on jquery.cookie.js after upgrade to 7.40
Status: Active » Closed (duplicate)
Related issues: +#594814: query.cookie.js 'Page Not Found' 406.shtml error

Can't help wondering why this problem has reared it's ugly head in the last day or so since the upgrade? Any ideas?

It could be a coincidence. That file has been in that place for years. Your hosting provider or sysadmins may have made a recent upgrade or web server configuration change. You could inquire about it.