Sidebar isn't visible on opportunity pages with children

[alanmoo]

https://network.mozilla.org/opportunity/2017-tech-policy-fellows/

[gvn]

Ok, this is completely baffling me.

The sidebar shows up in Firefox but not in Chrome or via a curl request. I even tried creating a new parent and subpage to see if Firefox had a cached copy and the result is the same.

Since this is generated on the server the only thing I can think of is user agent causing variances in the rendered HTML...but I have no idea why that would be the case.

[alanmoo]

Can you spoof the UA in Chrome and see if it does anything?

[gvn]

Changing UA to Firefox in Safari and Chrome didn't render the sidebar. Not surprised...

Also, this doesn't repro when I run the site locally.

[gvn]

Sidebar is now showing up on staging. I can't see anything in the last 2 commits that might have fixed this, but maybe a prod push will take care of things...

[gvn]

Ok, this has to be an environment variance issue.

Staging and prod are running identical code now and still only prod has this issue.

See:
https://network.mozilla.org/opportunity/test-parent/
versus
https://network.mofostaging.net/opportunity/test-parent/
in any non-FF browser

I also can't repro the issue locally.

[gvn]

@cadecairos Is there any way to generate a diff on network-api/app/networkapi/templates/pages/landingpage.html between our current production and staging builds?

[xmatthewx]

We're going to have a few new users of this multipage feature soon-ish. So good to dig into this.

[alanmoo]

I...think it works now?

[taisdesouzalessa]

Hey @alanmoo, the menu is sill not displaying in prod site - iPhone 7 (Firefox and Safari) - not sure about other phones, though.

[alanmoo]

The plot thickens. On desktop I see the sidebar...unless private browsing is turned on.

[alanmoo]

AHA! It doesn't show in private browsing because you're not logged in. I tested across devices/browsers and is indeed the issue: The secondary menu only appears if you're logged in to the back-end of Mezzanine. Let's make that not happen, and we'll be good across all these cases.

[taisdesouzalessa]

Mystery solved then? That was a good one!

[Pomax]

Are there steps to ensure an opportunity page when starting with a fresh clone?

[alanmoo]

I believe the PR that just landed this week should do it. python manage.py load_fake_data (See readme)

[alanmoo]

This has been resolved. Turns out it was the "published" vs "draft" status of the main Opportunity page causing problems. It has to be in Published mode.

[Pomax]

I am actually reopening this until we have issues filed to address where to find the information we uncovered, so this "never happens again" =)

[Pomax]

Follow up:

• implement something that highlights part of, or the entire chain of, pages are set to draft, which can cause the side menu to disappear. Tracked as Add Notice on display of Draft pages #984
• add an entry to our editor guide over on https://mzl.la/cms-guide that explains this situation in a "troubleshooting" section for mini-sites. Tracked as Add a troubleshoot entry to the editor guide for mini-sites/menu issues #987
• add an entry to the developer guide, which is really just the README.md, that lets devs find the editor guide as well, as they will need to be able to find this guide when doing user testing during development or as part of debugging. Tracked as Add https://mzl.la/cms-guide to the README.md #988