Support » Alpha/Beta/RC » Twenty Seventeen Theme Options menu disappears

  • Resolved Anthony Hortin

    (@ahortin)


    When live previewing Twenty Seventeen, and looking at the Front Page, there is a Theme Options option displayed in the Customizer.

    When you live preview another page on the same theme (e.g. the blog), the Theme Options option disappears.

    This is confusing.

    I understand that the Theme Options panel doesn’t relate to the Blog plage, but adding & removing different options in the Customizer depending on what page you’re live previewing is extremely confusing and annoying.

    This is what you see in the Customizer when on the front page…
    https://cl.ly/0p363O3u342f/o

    And this is what you see in the Customizer when on any other page…
    https://cl.ly/2B0T2g1X2f1d/o

    The other annoying thing is, if you’re actually viewing the Theme Options panel and then select another page in the Live Preview, this panel simply goes blank.
    https://cl.ly/2w112N102U1Y

Viewing 12 replies - 1 through 12 (of 12 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Plugin Review Team Rep

    Okay you only see Theme Options IF you have a custom Front Page set.

    Maybe that should be “Front Page Options” ?

    Whether it’s called “Front Page Options” or “Theme Options” is not the issue. The problem is that the actual customizer menu option was disappearing when you navigated to another page. Customizer options shouldn’t just appear/disappear depending on what page you’re currently Live Previewing.

    …and just to clarify, in all my screenshots above, the site was configured to use a static front page. i.e. Even with a static front page set, the customizer options disappeared when you previewed a page other than the front page.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Plugin Review Team Rep

    I disagree. If the options to customize are only useful on the front page, why would you want to edit them on other pages?

    I’ll give you a scenario…

    I’m live previewing my homepage and add in the various bits of content that I want to appear on the front of my site.

    I then click on my ‘About page’ to check that it’s displaying ok and while I’m there I think to myself, “Oh crap, I really should add my ‘About’ content to the homepage as well. I forgot to do that earlier”.

    I should be able to simply click back on the Theme Options customizer menu and then add in my ‘About’ page content that I forgot to add. Unfortunately though, I can’t because the Theme Options menu isn’t displaying! You’re forcing me to have to navigate back to the homepage again, just so that I can update some customizer options.

    This is just a simple scenario but one that I think is very relevant. You shouldn’t have to navigate to certain page in the live preview just so that you can update some of the theme options. It’s an inconsistent user experience.

    If I want to update some of the widgets on my site, I’m not forced to navigate to the blog page (where the widgets display). I can update them no matter where I am. Why should it be any different for any other option within the customizer. With your way of thinking, I should only be able to update the Sidebar widgets when viewing the blog page because that’s the only page they’re useful.

    (and yes, with all that said, I realise there are footer sidebars that display on each page, but even so, if those footer sidebars didn’t exist, I would still be able to update the Sidebar sidebar/widgets, no matter what page I am currently viewing in the live preview).

    Basically, I think it’s a really bad user experience if you start showing/hiding customizer options based on what page you’re actually viewing in the live preview.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Plugin Review Team Rep

    Basically, I think it’s a really bad user experience if you start showing/hiding customizer options based on what page you’re actually viewing in the live preview.

    I think it would be a bad UX to show options that don’t actually do anything to the page you’re viewing since the point of the live customizer is to customize lively πŸ™‚

    Customizer !== menus or widgets, remember.

    If I want to update some of the widgets on my site, I’m not forced to navigate to the blog page (where the widgets display)

    By default, widgets appear on all pages though, unless your theme has done something special. And that is actually what we’re doing here. If you had your theme set to only show sidebar widgets on posts and not pages, it would logically make sense not to display an option to edit widgets that aren’t on that page.

    We’ve asked the 2017 devs to peek into this, but honestly I had a suspicion that it’s just going to get a rename at this point, if anything.

    Well, I appreciate your comments, even though I don’t agree with them.

    I believe it’s confusing for the end user to start hiding/showing options base on what page is currently being previewed. I just hope this is only something that is specific to Twenty Seventeen and not behaviour that is going to be commonplace in the Customizer in general.

    Customizer !== menus or widgets, remember

    I’m not entirely sure what you actually mean by this. Menus & widgets are now in the Customizer so they’re all part of the Customizer experience. You can’t have part of the Customiser performing one way and another part performing another way. There needs to be consistency across the whole Customizer experience. If you believe that the “Customizer !== menus or widgets” then why have they been implemented in the Customizer then?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Plugin Review Team Rep

    I mean that Customizer isn’t like the Appearance -> Widgets page, where you see ALL the widgets. It’s not meant to show everything at once.

    Contextual data isn’t a bad thing πŸ™‚

    FWIW, it’s totally specific to 2017, and not the customizer, but since this theme demonstrates that you can make items contextual, I imagine people will start doing it.

    I mean that Customizer isn’t like the Appearance -> Widgets page, where you see ALL the widgets.

    Ok. Yep, I realise it’s not the same sort of layout as the original Widgets page. My example was more pointing to the fact that other customizer options (such as the Widgets panel), aren’t affected by what page is currently being previewed, and will allow you to edit the options regardless of what page is currently being live previewed.

    I’m glad it’s only specific to Twenty Seventeen, but I still think it’s a horrible decision to implement something like this and I really hope other themes don’t follow. I can just imagine a scenario where you have to live preview every single page on your site just to make sure that you’ve seen all the theme options, purely because some pages show some options, and then other pages show completely different options. When you first enter the Customizer, you should be able to see every option available to you, and not have to navigate to certain pages just so that you can edit the customizer options.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Plugin Review Team Rep

    So I did some more testing… This is totally a theme choice. I found the exact same behavior on 4.6 with another theme.

    I understand you not liking it, and why it’s confusing, but it’s the way folks chose to do it. This is (surprisingly) not a new feature.

    Now I am certainly not at your level from a development perspective, but I’m a pretty good application guy.

    IMHO – this functionality is confusing. Very confusing. At first when I watched the tutorial I thought, wow! Someone’s finally got it right! I theme that is pre setup to look great out of the box that I could just make a few touchups to regarding written content and run with it.

    Then I attempted to change the Home Page text and BAM! I lost the look and feel that I loved so much. So, not knowing what I did to make it disappear I started again by deleting my DB. Now I started to watch carefully what I was doing to make the theme change so drastically. That’s when I noticed that when I create a single new About page (under Pages) I would loose the scrolling page AND I noticed when that disappeared so did my Theme Options tabs. So, now I thought I was on to something, I Google and found this article and thought, NP, after I read this I’ll understand what I did. Well, I’ve spent the last two hours trying to sort out the logic of what’s going on and I can’t.

    I’m hoping for a reply (in layman’s terms) that will allow me to understand how this theme is suppose to work. In short, I thought it looked pretty cool, but if one needs to think like a developer to use it – then it simply won’t get used – (again MHO) because most developers will want to (and be able to) roll their own for the sake of uniqueness.

    Cheers! (and thanks for listening)
    Franko

    Still thinking about this:

    Now, all I did was create a new About page, something that should have been unrelated – or at least that’s what I think. So, here’s an idea, instead of making the tab Theme Options non-visible for pages (or views) where you feel it has not purpose – why not leave the tab visible and when you click on it describe why there are no Theme Options for this view or page.

    The idea being, a UI is way more enjoyable to use when it teaches you in bite sized pieces as it is being used.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Twenty Seventeen Theme Options menu disappears’ is closed to new replies.