Make WordPress Core

Opened 18 years ago

Closed 18 years ago

Last modified 9 months ago

#3467 closed defect (bug) (invalid)

commenting in post preview window breaks site

Reported by: corourke's profile corourke Owned by: rob1n's profile rob1n
Milestone: Priority: low
Severity: minor Version: 2.0.5
Component: Administration Keywords:
Focuses: Cc:

Description

When posting a comment in an unpublished post preview window and then publishing the post the site will stop responding. Both the front and backends become unreachable.

The only way to resolve this issue is to find the relevant post in the database and remove it and/or deleting the blog.

This appears to be a bug (risk) with Wordpress MU 1.0 as well. Obviously this isn't something the average user would usually do but it is still a critical issue.

Change History (10)

#1 follow-up: @Viper007Bond
18 years ago

Why in the hell would you post a comment in the preview window?

#2 in reply to: ↑ 1 @JeremyVisser
18 years ago

Replying to Viper007Bond:

Why in the hell would you post a comment in the preview window?

Why you would do it is irrelevant. It's possible to do, and it triggers a bug.

I confirm that the comment does not post successfully in the preview window, but was not able to break my site running on /trunk/. The only thing "broken" was that the post preview iframe went blank. After a refresh, it went back to normal, but the comment was not posted.

#3 @foolswisdom
18 years ago

  • Severity changed from critical to minor

ENV: WP 2.0.6-beta-1
I experienced the behavior described by Jeremy.
Lowering severity to minor

corourke, can you explain what you mean by "Both the front and backends become unreachable."? Any diagnostic data?

#4 @Viper007Bond
18 years ago

  • Component changed from General to Administration
  • Priority changed from normal to low

#5 @foolswisdom
18 years ago

  • Milestone 2.2 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Closing as WONTFIX for now. How preview is done is likely to be redesigned in future version.

#6 follow-up: @rob1n
18 years ago

  • Milestone set to 2.2
  • Resolution wontfix deleted
  • Status changed from closed to reopened

How soon are we talking? If previews are going to be reworked after 2.2, then this should be worth fixing. While the idea of commenting in a preview post to me is stupid to say the least, I think we should add a check. You never know what those users do.

#7 @rob1n
18 years ago

  • Owner changed from anonymous to rob1n
  • Status changed from reopened to new

#8 @rob1n
18 years ago

  • Status changed from new to assigned

#9 in reply to: ↑ 6 @foolswisdom
18 years ago

  • Milestone changed from 2.2 to 2.3

Replying to rob1n:

While the idea of commenting in a preview post to me is stupid to say the least,

I think we should add a check.

The problem as I experienced it was cosmetic.

#10 @rob1n
18 years ago

  • Milestone 2.3 deleted
  • Resolution set to invalid
  • Status changed from assigned to closed

Ah, my bad. Seems like bad reporting. Reclosing.

Note: See TracTickets for help on using tickets.