Newspaper Mobile Menu Not Working: Find Out Which Front End Owns the Hamburger

Three ways Newspaper can draw a phone header

Most themes have one header that squeezes onto a phone. Newspaper has up to three, and tagDiv's own staff list them when owners ask: the responsive version edited in tagDiv Composer, optional mobile pages, and the bundled tagDiv Mobile Theme plugin. Each draws its own hamburger. Fixing the wrong one is how owners spend an afternoon changing settings that phones never read.

To learn which one your phones get, open the homepage on a real phone, logged out. tagDiv's documentation says the Mobile Theme replaces the homepage with a grid of three featured posts and a latest articles section. If your phone shows that layout, you are debugging the Mobile Theme. If it shows a narrow copy of your desktop design, you are debugging the Composer header. Write the answer down before touching anything.

The five shapes of a broken Newspaper hamburger

• The tap does nothing. The icon is there and ignores you. This is a script that has not run, almost every time.
• The page shrinks to one side behind a grey layer, with no menu in it. The script ran and opened the panel, but the panel's styles did not arrive. One owner in 2022 traced exactly this to a CDN serving the theme stylesheet.
• There is no icon at all, but tapping the corner opens the menu. tagDiv staff have answered this one: the icon is the same color as the header behind it.
• The panel opens with the wrong links, or none. The menu assignment is wrong for the front end your phone is using.
• Desktop visitors see the phone layout, or phones see the desktop header. A cache is handing one device's page to the other.

Note also where it fails. A 2019 forum thread described a menu that broke on the homepage but worked on posts, and staff pointed at untested plugins and a stale demo image. A fault on one template only is a clue that something on that template, an ad, an embed or a block, is involved.

Likely causes, ranked for Newspaper, with a test for each

1. An optimizer delayed or merged tagDiv's menu scripts

In a 2021 forum thread about WP Rocket's Delay JavaScript Execution, a tagDiv staff member listed the files that drive the menu: tagdiv_theme.min.js inside the tagDiv Composer plugin (one copy for the main theme, one under its mobile folder for the Mobile Theme), js_files_for_front.min.js from tagDiv Cloud Library, and tagdiv-theme.min.js in the theme folder. Owners who excluded those files still reported a menu that only worked while logged in. Treat that list as a starting point, because version 12.6 changed things: its changelog says specific JS files are now loaded only when needed.

There is a fair counterpoint. When we loaded tagDiv's Newspaper Pro demo in October 2026, it was running WP Rocket with delayed scripts itself. So delay is not fatal by design. An untested combination is. The test is simple: switch off delay, defer and combine for JavaScript, purge every cache, and tap the menu on a phone. If Cloudflare sits in front of the site, turn off Rocket Loader too, which tagDiv staff have advised in menu threads.

2. A cache that does not know phones from desktops

This one bites Mobile Theme sites. tagDiv's Mobile Theme guide says that with any cache plugin other than WP Super Cache, you must enable that plugin's mobile cache option, or the Mobile Theme can show on desktop too. The reverse happens as well: phones get a cached desktop page whose menu was never meant for them. Check your cache plugin for a separate mobile cache setting and turn it on.

3. The menu is assigned in the wrong place

On the Mobile Theme, a tagDiv staff member gave the path in 2023: Theme Panel > Mobile Theme > Header, then pick the main menu, save, and clear every cache. On a responsive site, the menu comes from the Mobile Menu element in the header template's mobile zone; tagDiv's mobile header guide says its general settings choose which menu it shows. Panel labels move between releases, so match these names against your own Theme Panel.

4. The icon is there, painted invisible

A white icon on a white header looks exactly like a missing menu. Staff fixed a 2023 case by opening the header in Composer, switching to the phone viewport and changing the hamburger icon color. Long-press the corner where the icon should be. If something opens, this is your problem.

5. The stylesheet was moved or blocked

The grey-layer symptom points here. The 2022 owner whose page shrank sideways fixed it with help from WP Rocket's support by excluding wp-content/themes/Newspaper/style.css from RocketCDN. That is one owner's report, not tagDiv guidance, but the test is general: open the browser's Network tab and confirm every stylesheet returns a 200. Missing styles get their own page, Newspaper CSS not loading.

Tablets fall between the two headers

tagDiv Composer works to four bands, which a staff member listed in 2025: phones up to 767 pixels, portrait tablets from 768 to 1018, wider tablets from 1019 to 1140, and desktop above. Changing them means rebuilding the theme, which tagDiv does not support. The header switch sits at the first line, so an upright tablet gets the desktop header and desktop menu. If that menu has eight long items, it wraps or overlaps the logo, and owners report a mobile menu fault.

Open the header template in Composer, click the tablet portrait viewport and look at the desktop zone at that width. Shorten labels, reduce items, or set a smaller font for that viewport. If you want a hamburger on tablets too, that is a design change to the header template, not a setting, and it belongs in a planned edit rather than a midnight fix. Our Newspaper header not showing page covers how the zones are assigned.

Getting the menu back without losing the speed work

1. 1

   Name the front end

   On a real phone, logged out, decide whether you are seeing the Mobile Theme, a mobile page or the responsive header. Every later step depends on it.

2. 2

   Read the console from the phone

   Connect an Android phone to Chrome's remote debugging, or an iPhone to Safari on a Mac. Tap the menu and note the first red error and its file. A path under td-composer or td-cloud-library is tagDiv's code; a path under a cache folder means an optimizer bundled it.

3. 3

   Switch off script optimization

   Disable delay, defer and combine for JavaScript in your optimizer, turn off Cloudflare Rocket Loader, then purge the plugin cache, the host cache and the CDN. Test again on the phone.

4. 4

   Fix the menu assignment

   On the Mobile Theme, choose the main menu under the Mobile Theme header settings in the Theme Panel and save. On the responsive header, open the template in Composer's phone viewport and check the Mobile Menu element's menu and icon color.

5. 5

   Separate the mobile cache

   If the Mobile Theme is active and your cache plugin is not WP Super Cache, enable its mobile cache option so phones and desktops get their own copies.

6. 6

   Bring speed back one switch at a time

   Turn optimization features back on singly, testing the menu after each. Keep any that pass. For the one that breaks the menu, try excluding the tagDiv files your console named; if that fails, leave that feature off.

7. 7

   Update, then retest

   Older releases carry menu fixes: 12.2 fixed scrolling on mobile menu and mobile search clicks, and 12.6.2 fixed glitching sticky rows in the mobile header. Update on a staging copy first, following our Newspaper update problems routine.

Keeping the phone menu honest after every change

• Tap the menu on a real phone, logged out, after every theme update, plugin update or optimizer change. Administrators often skip optimization, so your own phone may lie while you are signed in.
• Decide on one mobile approach. Running the Mobile Theme and a carefully tuned responsive header at once doubles the testing for little gain.
• Keep a written list of every script exclusion and why it exists, stored where the next person will find it.
• Retest after changing a header template, because the mobile zone is a separate set of elements that is easy to forget.
• Check an article, a category page and the homepage, since templates differ and a fault can live in one of them.

If the menu works but feels sluggish, that is a speed problem, not a breakage, and the Newspaper speed guide covers what competes with it on a phone. The general mechanics of dead hamburgers across themes are in WordPress mobile menu not working. When a console error names a script you do not recognize, Newspaper JavaScript errors goes file by file, and if the editor itself will not open, see tagDiv Composer not loading.

When three front ends are two too many

A publication's phone menu on Newspaper passes through the theme, two tagDiv plugins, possibly a second theme for phones, a cache that must tell devices apart, an optimizer that rearranges the scripts, and a CDN that copies the result. Each layer is reasonable. Together they make the menu the most fragile thing on the site, on the screen where many readers arrive from search and social links.

Newspaper gives phones up to three front ends. Your readers only need one that works.

A Next.js build has one: a menu component in the same codebase as everything else, tested in a build before it deploys, with nothing rewriting its scripts on the live server. It costs more up front and needs a developer for layout changes. Newspaper vs Next.js weighs that trade for publishers, and Newspaper to Next.js shows how an archive moves with its URLs kept. If you would rather keep Newspaper, our theme troubleshooting service finds the failing layer on a fixed quote, and the Newspaper repair hub collects the other known faults. More theme fixes live in the troubleshooting section.