The menu won't open on my phone

On a computer the site looks fine, because the full menu is on show across the top. On a phone the pages hide behind a small button - usually three lines in a corner - and on a moved site that button is the single most likely thing to be broken. You tap it and nothing happens. Or something happens, but no menu you can see.

Either way, visitors on phones can't get past your homepage. That's most visitors, so this is worth fixing the day you notice it.

Why it happens

The old site opened that menu with its own code, and bernard doesn't carry old code across - it's the main way a moved site can become unsafe. Instead, every moved site gets bernard's own replacement wiring: it finds menu buttons, opens the right menu when tapped, and if it can't find a menu to open at all, it puts in a clean spare menu of its own so phone visitors are never stranded.

That covers most sites. But menus are built in wildly different ways, and some defeat the automatic repair. Those show up as one of a few symptoms:

• Tap and nothing happens. The button was never connected to the menu it's meant to open. The fix is usually small: point the button at the right menu.
• Tap and the menu opens invisible, or as a bare unstyled list. The connection works, but the styling for the open menu didn't survive the move - the move only ever saw it closed. The fix is to give the open menu simple styling of its own, not to chase the old site's styling.
• The menu opens but won't close, or sits open when the page loads. The wiring fires more than once, or the open state got stuck. A fix here isn't done until the menu has been seen to open and close.
• There's no menu button on the phone at all. The phone version of the header never made it across. The spare menu handles most of these; if it hasn't appeared, say so.

What to ask

Say what you did and what you saw, and name the device:

On my phone, the menu button on my homepage does nothing when I tap it. Check on a phone-size preview that the menu really opens and closes, fix whatever is wrong, and show me before it goes live.

The phone part matters: this class of problem is often invisible on a computer, where the full menu shows without any button. If you can, add which symptom you're seeing - dead button, invisible menu, stuck open - but "it doesn't work when I tap it" is enough. Point at exactly what you want changed helps if you're not sure how to describe the button.

How a proper fix goes

Whether it's you asking in the workshop or an assistant working on your site for you, the shape of a trustworthy fix is the same:

1. Reproduce it first. Tap the button on a phone-size preview of the draft and record what actually changed. Not "the button looks fine" - what happened when it was pressed. A menu problem can't be diagnosed by reading alone, because the page may look correct while doing nothing.
2. Smallest fix first. Connect the button to its menu; if the open look is gone, style the open state simply and freshly.
3. Rebuild if repair won't hold. A simple, self-contained menu that lists your pages and matches your site's look beats a fragile repair of the old one. It belongs to the new site, so there's nothing left of the old code to break.
4. Prove it the same way it was found. Tap again: it opens, it closes, and there's a picture of the open menu to show for it. A menu wedged permanently open is not a fix, and neither is one that was edited to look open without the tap ever working.

You'll see the working menu on a preview before anything reaches your live site.

Slideshows, tabs and other things that stopped moving

The same stripped-code story breaks more than menus: slideshows that sit dead, tabs showing every panel at once, sections that never appear. Those look different and are fixed differently - see Part of my page is blank, or a slideshow does nothing for that family. And if a fix doesn't hold or something still feels wrong, Something went wrong and I want to tell someone gets it looked at properly.