WordPress.org

Make WordPress Core

Opened 14 months ago

Closed 8 months ago

#23455 closed defect (bug) (duplicate)

Theme Customizer does not load when static Front Page is moved to Trash

Reported by: jeherve Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.4
Component: Appearance Keywords:
Focuses: Cc:

Description

Steps to reproduce:

  1. Go to Pages > Add New, and publish a new page
  2. Go to Appearance > Themes > Customize
  3. Under Static Front Page, set this new Page as your Front Page. Save changes
  4. Go to Pages > All Pages, and trash the page
  5. Go back to the customizer

When commenting out $this->handle_404(); in wp-includes/class-wp.php#L550, the Preview appears again, but generates quite a lot of notices.

Tested with WordPress Trunk (Version 3.6-alpha-23400)

Change History (13)

comment:1 follow-up: helen14 months ago

  • Keywords reporter-feedback added

What happens on the front when you trash the front page? Seems like the customizer is loading fine, and it's probably showing the front just as it is.

comment:2 in reply to: ↑ 1 westi14 months ago

Replying to helen:

What happens on the front when you trash the front page? Seems like the customizer is loading fine, and it's probably showing the front just as it is.

What happens in my testing is the request for all the customiser data gets the 404 page not found content not the customiser data content and the customiser never loads properly.

comment:3 helen14 months ago

I guess I thought of it as the customizer loading fine, but I see that the front shows a 404 instead of just a white screen now (I was probably doing something weird earlier).

comment:4 jeherve14 months ago

  • Keywords reporter-feedback removed

I also see a 404 page on the front.

comment:5 richardmtl14 months ago

  • Cc richardmtl added

comment:6 designsimply14 months ago

Confirmed using jeherve's steps. Live previews fail if you've trashed the static front page, but I also noticed that both the front page and the posts page have to be blank to trigger the problem.

Here's the error I see if "A static page" is selected and both the "Front page" and "Posts page" are blank in Settings → Reading:

Failed to load resource: the server responded with a status of 404 (Not Found)

http://f.cl.ly/items/1c0r3j1g2E321T1O2v47/Screen%20Shot%202013-02-12%20at%202.42.23%20PM.png

Tested with WordPress trunk r21780.

If you leave "Front page" blank and select a "Posts page," the front page setting is ignored and the latest posts are displayed on the front end and in the customizer. Could the same behavior happen if both of those settings are blank?

comment:7 zoonini12 months ago

  • Cc zoonini added

comment:8 jkudish12 months ago

  • Cc jkudish added

comment:10 nacin9 months ago

Seems like this is a larger issue than just the customizer.

comment:11 nacin9 months ago

  • Version changed from trunk to 3.4

comment:12 c3mdigital8 months ago

  • Keywords has-patch added; needs-patch removed

Patch on #24171 tested and also fixes this bug.

comment:13 SergeyBiryukov8 months ago

  • Keywords has-patch removed
  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Looks like this is not specific to the customizer. Going to close as a duplicate of #24171.

Note: See TracTickets for help on using tickets.