Make WordPress Core

Opened 13 years ago

Closed 13 years ago

#3397 closed defect (bug) (wontfix)

Occasional dbx.js cookie-related JS error

Reported by: Viper007Bond Owned by: markjaquith
Milestone: Priority: normal
Severity: critical Version: 2.0.5
Component: Administration Keywords:
Focuses: Cc:
PR Number:


From time to time, I get a Javascript error from dbx.js and the only way to fix it delete the cookie. No idea what causes it, but it seems to happen randomly and has been happening for quite some time. I'm using Firefox and it happened on both 1.5.x and 2.0.

Here's the Javascript error that occurs:

Error: this.cookie[i][1] has no properties
Source File: http://localhost/wordpress-2.0.x/wp-includes/js/dbx.js
Line: 6

Attachments (1)

dbx_205_branches_20.diff (36.8 KB) - added by markjaquith 13 years ago.
Patch for branches/2.0/

Download all attachments as: .zip

Change History (19)

#1 @Viper007Bond
13 years ago

The cookie is dbx-postmeta and it happens on both my local server and my blog (I think, hard to remember).

#2 @foolswisdom
13 years ago

When you say for some time, do you recall if you saw it prior to 2.0.5 ?

#3 @Viper007Bond
13 years ago

Yes, it's been happening for a couple versions now.

#4 @markjaquith
13 years ago

  • Keywords needs-patch added
  • Owner changed from anonymous to markjaquith
  • Status changed from new to assigned

Clarification: 1.5.x and 2.0 are WP version numbers, not FF numbers, right?

Attn: Andy Skelton, Robert Deaton

I'm no JS guru, but I think this happens when you try to access the cookie's values when the cookie isn't set, so you might be able to fix it by checking <<<this.cookie>>> first.

#5 @Viper007Bond
13 years ago

I mean FF versions. This JS didn't exist in WP v1.5.x. ;)

#6 @markjaquith
13 years ago

Doh! Also note that in that comment I forgot the code syntax for Trac. It was late.

It appears that we're using DBX 2.01 but 2.05 is the current version. Maybe upgrading will fix that error. Patch coming.

13 years ago

Patch for branches/2.0/

#7 @markjaquith
13 years ago

  • Keywords has-patch added; needs-patch removed

There's a patch for /branches/2.0/

Trunk is already using DBX 2.05

Viper007Bond: have you experienced this problem while using 2.1 or WP.com?

#8 @markjaquith
13 years ago

Ping Ryan/Andy:

Can DBX be upgraded independently of TinyMCE? The commit that upgraded DBX in trunk also upgraded TinyMCE. What's the rating for updating DBX on the "potential breakage meter" ?

We also need a 2.0.7 milestone already.

#9 @markjaquith
13 years ago

  • Milestone changed from 2.0.6 to 2.0.7
  • Priority changed from high to normal
  • Severity changed from blocker to critical

Let's put this off until 2.0.7 If we get to 2.0.7 and no one has seen this issue pop up in 2.1, then we'll know that a DBX upgrade is the cure.

#10 @Viper007Bond
13 years ago

Haven't had it happen in 2.1, just had it happen in latest 2.0.x.

#11 @intoxination
13 years ago

The problem I have noticed is if you install Wordpress twice in the same domain/sub-domain. If that happens, the cookies from both installs conflict with each other. This problem only seems to occur on 2.0.X. The 2.1 branch is not affected (I have 3 copies on the same domain with no problem).

#12 @markjaquith
13 years ago

We'll look at a DBX upgrade for 2.0.7

#13 @markjaquith
13 years ago

  • Milestone changed from 2.0.7 to 2.0.8

#14 @marcfonteijn
13 years ago

I've just updated dbx.js from 2.01 to 2.05 and that fixes the problem for me. I'm currently on WP 2.0.9

#15 @markjaquith
13 years ago

DBX 2.0.5 has been in 2.1 for a long time without any complaints. I think this is safe.

#16 @markjaquith
13 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [4957]) Upgrade DBX to version 2.0.5 to fix occasional cookie error. fixes #3397

#17 @foolswisdom
13 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

DBX 2.05 seems to cause severe bug #3895: Reloading the post editing screen in Firefox turns a post from Published to Private

#18 @markjaquith
13 years ago

  • Keywords has-patch removed
  • Milestone 2.0.10 deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

Reverting. No longer considering this for 2.0.x


Note: See TracTickets for help on using tickets.