WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 7 years ago

#5308 closed defect (bug) (duplicate)

continued cookie error after upgrade to 2.3.1

Reported by: openlycreative Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3.1
Component: General Keywords: cookie error
Focuses: Cc:

Description

After upgrading to WP 2.3 I (like everyone else) was experiencing the "cookie error" every time I logged into my site. When WP 2.3.1 was released I assumed that the new upgrade would fix the cookie errors, but it hasn't. Not matter on what computer or with what browser I try it with I always get the cookie error.

I wasn't sure if any of the patches would work on 2.3.1 so I haven't tried them. I did however, try to see if my wp_config.php file had spacing issues and it didn't.

I'm not sure what the next step is to fix this issue. Can I get some help?

Change History (7)

comment:1 @openlycreative7 years ago

I am really not happy with the lack of support on this issue. I have been using WordPress for quite a while now and have had several issues with lack of response to issues on the message boards in the past and (apparently) here as well.

I don't want to have to sink several hundred dollars into a CMS if I don't have to, but the lack of support is a big problem for me. This "cookie error" is causing problems for my clients and I just can't have that.

Opensource is great, but only if there is a dedicated staff to debug these kinds of issues.

comment:2 @pishmishy7 years ago

Please can you precisely describe how to replicate the "cookie error", we can then work on fixing the problem.

comment:3 @foolswisdom7 years ago

openlycreative, I understand your frustration. People tend to prioritize their work based on their own needs and interests. Your note reads a little bit like you are looking for something for nothing -- I imagine in reality you have contributed a lot to WordPress through promoting and deploying to your clients.

if it is costing you money than I suggest you spend money on a solution and give the solution back to the community. Email the wp-pro list with a request for quote.

Otherwise as pishmishy suggests, we will need a reproducable scenario. If you can duplicate the issue with a fresh install from multiple browsers from multiple computers than it suggests it might be specific to the server environment -- one of the cookie issues was just that, where installing to a subdirectory was a factor.

comment:5 in reply to: ↑ 4 ; follow-up: @pishmishy7 years ago

Replying to Michaelh:

Links to related forum topics:

Thank you for the links. Unfortunately your posts to the forum don't contain information on how we can replicate the issue so we can work on fixing it. Once I can replicate your problem I'd be happy to work on fixing it.

comment:6 in reply to: ↑ 5 @pishmishy7 years ago

Problem may be related to #5076 ?

comment:7 @lloydbudd7 years ago

  • Milestone 2.5 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Assuming this relates either to #5076 mentioned by pishmishy or #5365. Closing as duplicate.

Note: See TracTickets for help on using tickets.