WordPress.org

Make WordPress Core

Opened 12 years ago

Closed 12 years ago

#10338 closed defect (bug) (worksforme)

Auto-save auto-updates published pages

Reported by: bilge Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.8
Component: Autosave Keywords: autosave publish update
Focuses: Cc:

Description

If I begin editing a page that has previously been published then every time the editor auto-saves the page, it is reflected immediately on the live site without waiting for me to republish the changes.

Change History (9)

#1 @ryan
12 years ago

Have you looked while not logged in? Maybe you are seeing the preview.

#2 @bilge
12 years ago

I find that highly unlikely since I'm actually querying the results directly with:

		query_posts(array(
			'post_type' => 'page',
			'post_status' => 'publish',
			'orderby' => 'menu_order',
			'order' => 'ASC',
			'posts_per_page' => -1,
		));

#3 follow-up: @mrmist
12 years ago

In current trunk the changes are only displayed for me once I press "update".

Tested by making changes in one browser which were auto-saved, then viewing the entry in another browser (not logged in).

#4 in reply to: ↑ 3 ; follow-up: @bilge
12 years ago

Replying to mrmist:

In current trunk the changes are only displayed for me once I press "update".

Does "current trunk" mean version 2.8? This is the current stable version, which I am using.

#5 in reply to: ↑ 4 ; follow-up: @mrmist
12 years ago

  • Version set to 2.8

Replying to bilge:

Does "current trunk" mean version 2.8? This is the current stable version, which I am using.

No it's the current source as in the svn repository, so roughly the 2.8.1 beta.

#6 in reply to: ↑ 5 @bilge
12 years ago

Replying to mrmist:

Replying to bilge:

Does "current trunk" mean version 2.8? This is the current stable version, which I am using.

No it's the current source as in the svn repository, so roughly the 2.8.1 beta.

If it's fixed, then great, but someone still needs to confirm the issue in 2.8 first, particularly since I didn't notice any fix in the change log for this issue.

#7 follow-up: @mrmist
12 years ago

Even in 2.8 I do not see the behaviour you are describing if I browse after a post has been auto-saved.

#8 in reply to: ↑ 7 @bilge
12 years ago

Replying to mrmist:

Even in 2.8 I do not see the behaviour you are describing if I browse after a post has been auto-saved.

Then please try applying the query in reply #2.

#9 @westi
12 years ago

  • Milestone Unassigned deleted
  • Resolution set to worksforme
  • Status changed from new to closed

I have tested this with the query_posts call and I do not see this either when logged in or not logged in (tested from two different browsers one logged / one not logged in)

Note: See TracTickets for help on using tickets.