[wp-trac] [WordPress Trac] #27347: Widget Customizer: Only Widgets of Child Theme Editable, Parent Theme Widgets Missing

[WordPress Trac]

#27347: Widget Customizer: Only Widgets of Child Theme Editable, Parent Theme
Widgets Missing
--------------------------+--------------------
 Reporter:  daveshine     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.9
Component:  Widgets       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+--------------------

Comment (by westonruter):

 Replying to [comment:1 nacin]:
 > I'm pretty sure it only displays sidebars that appear on the page you're
 on. It's a cool idea in theory, but it can be confusing (and some widget
 areas are pretty buried due to context, forcing someone to click around in
 the preview window so they can edit it). It might be worth showing these
 not-being-previewed widget areas but with some kind of indication they're
 not shown on that particular page.

 Correct. Customizer sections for widget areas only appear on previewed
 URLs that contain that widget area (sidebar) used in the template (i.e.
 `dynamic_sidebar()` is used). By hiding the sections for widget areas not
 shown in the preview, we can conserve a lot of space in the customizer. If
 all widget area sections are always shown, the sidebar would be very
 cluttered.

 One solution would be to include some messaging to direct users that they
 should navigate to the page that has the sidebar in use and then enter the
 customizer from there. They can either navigate to this page from within
 the customizer or from the frontend and click the link in the admin bar.

 Alternatively, or complementarily, all the widget area sections should be
 grouped into one meta section, as shaunandrews has proposed. With this in
 place, there could be a checkbox/button to toggle between showing only the
 widget areas currently used in the previewed URL, or to show all of the
 widget areas regardless but with some additional indicator (such as being
 faded out).

 Originally discussed at https://github.com/x-team/wp-widget-
 customizer/issues/77

 @nacin: Shall I create a new Trac ticket for this with the expectation it
 would be part of a post-3.9 milestone?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27347#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform