Ticket #3397 (closed defect: wontfix)

Opened 2 years ago

Last modified 1 year ago

Occasional dbx.js cookie-related JS error

Reported by: Viper007Bond Assigned to: markjaquith
Priority: normal Milestone:
Component: Administration Version: 2.0.5
Severity: critical Keywords:
Cc:

Description

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

dbx_205_branches_20.diff (36.8 kB) - added by markjaquith on 11/29/06 09:09:05.
Patch for branches/2.0/

Change History

11/28/06 01:52:54 changed by Viper007Bond

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

11/28/06 02:07:01 changed by foolswisdom

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

11/28/06 05:15:05 changed by Viper007Bond

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

11/29/06 00:06:42 changed by markjaquith

  • keywords set to needs-patch.
  • 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.

11/29/06 07:59:22 changed by Viper007Bond

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

11/29/06 08:31:36 changed by markjaquith

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.

11/29/06 09:09:05 changed by markjaquith

  • attachment dbx_205_branches_20.diff added.

Patch for branches/2.0/

11/29/06 09:10:36 changed by markjaquith

  • keywords changed from needs-patch to has-patch.

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?

12/04/06 13:37:46 changed by markjaquith

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.

12/05/06 05:29:24 changed by markjaquith

  • priority changed from high to normal.
  • severity changed from blocker to critical.
  • milestone changed from 2.0.6 to 2.0.7.

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.

12/16/06 05:47:00 changed by Viper007Bond

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

12/16/06 14:17:18 changed by intoxination

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/16/06 16:47:19 changed by markjaquith

We'll look at a DBX upgrade for 2.0.7

01/11/07 04:51:36 changed by markjaquith

  • milestone changed from 2.0.7 to 2.0.8.

03/01/07 09:59:25 changed by marcfonteijn

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

03/02/07 07:12:33 changed by markjaquith

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

03/02/07 07:14:02 changed by markjaquith

  • status changed from assigned to closed.
  • resolution set to fixed.

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

03/06/07 00:24:15 changed by foolswisdom

  • status changed from closed to reopened.
  • resolution deleted.

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

03/07/07 05:16:56 changed by markjaquith

  • keywords deleted.
  • status changed from reopened to closed.
  • resolution set to wontfix.
  • milestone deleted.

Reverting. No longer considering this for 2.0.x

[4989]