WordPress Navigation Menu Not Saving? 15 Fixes That Work

A laptop showing a website dashboard with a menu panel beside a notebook — wordpress navigation menu not saving fix guide
Menu edits that vanish after saving usually mean the save never reached the database, not that the menu itself is broken.

You drag menu items into place, click Save Menu, and the page reloads with your old menu staring back at you. When wordpress navigation menu not saving happens, every edit feels wasted: new items disappear, reordering undoes itself, and deleted items return like nothing happened. The menu itself is rarely broken. The save is usually blocked by a server limit, a plugin conflict, a cache showing old content, or the wrong menu assigned to the theme location.

This guide works through the causes in order, from re-saving carefully to rebuilding the menu from scratch. Nothing here deletes your pages or posts, and the deeper fixes include a backup step first. Work through the fixes one at a time, and check the live site in a fresh browser tab after each one. A menu that stays changed after a refresh is the proof that counts.

Table of Contents

  • Why This Error Happens
  • Quick Checks
  • Diagnosing the Problem
  • Fix 1: Save the Menu Again and Watch for the Confirmation Notice
  • Fix 2: Clear the Browser Cache and Try a Different Browser
  • Fix 3: Check the Menu Is Assigned to the Right Theme Location
  • Fix 4: Save Small Changes in Batches Instead of One Large Save
  • Fix 5: Raise the PHP Input Limit for Large Menus
  • Fix 6: Clear the Site Cache, Server Cache and CDN Cache
  • Fix 7: Test for a Plugin Conflict in Troubleshooting Mode
  • Fix 8: Switch Briefly to a Default Theme
  • Fix 9: Save the Menu From the Customizer Instead
  • Fix 10: Edit the Menu With the Navigation Block in the Site Editor
  • Fix 11: Check Your User Role Has Permission to Edit Menus
  • Fix 12: Fix the JavaScript Error That Blocks the Save Button
  • Fix 13: Check Site Health and Repair the Database Tables
  • Fix 14: Delete and Rebuild the Damaged Menu
  • Fix 15: Update WordPress, the Theme and Plugins, Then Re-Save
  • What to Avoid
  • Frequently Asked Questions
  • Conclusion
  • Helpful Official Resources

Why This Error Happens

Saving a menu sends every menu item, its order, its parent, and its settings to the server in one request, and WordPress writes them all to the database. If the request is too large, if a script error stops the button working, or if the database write fails, WordPress shows the old menu again with no clear error. These are the reasons that happens most often.

1. The Save Request Is Too Large for the Server Limit

Every menu item adds fields to the save request, and large menus with many items and submenus can exceed the server’s max_input_vars limit. When the limit is hit, the server silently drops the extra fields, and WordPress saves only part of the menu — or appears to save nothing at all. This is the most common cause of wordpress navigation menu not saving on sites with big menus, and it produces no error message to point at the cause.

2. A Plugin Breaks the Menu Editor JavaScript

The menu editor relies on JavaScript for dragging, expanding, and saving items. A plugin that loads a broken script, an outdated jQuery copy, or a conflicting admin script can stop the editor working while the rest of the dashboard looks fine. The Save button may do nothing, the page may reload without saving, or items may refuse to drag. Plugin conflicts are the most common cause on sites where the menu used to save and suddenly stopped.

3. The Theme Does Not Support the Menu Location

A menu only appears on the site when it is assigned to a theme location the active theme actually supports. If the theme was changed, or if the menu was never assigned, the save can succeed in the dashboard while the live site shows a different menu — or no menu at all. The edit is not lost; it is saved to a menu the theme never displays. Checking the assignment is a two-minute test that ends a lot of confusion.

4. A Cache Shows the Old Menu After a Successful Save

Caching plugins, server caches, and content delivery networks all store copies of pages, including the header with the menu. After a successful save, visitors — and the site owner — can keep seeing the cached old menu for hours. The save worked, but the cache hides the result, so the owner saves again and again, convinced the save failed. Clearing every cache layer is the only reliable test.

5. The Wrong Menu Is Assigned to the Location

Sites often have several menus: a main menu, a footer menu, a mobile menu, and test menus left over from building the site. Editing one menu while the theme displays another produces the exact symptom of a failed save: the dashboard shows the edits, the site shows the old menu. The Manage Locations tab shows which menu each location uses, and a mismatch there explains the whole fault.

6. A Database Error Silently Drops the Save

Menu items are stored as posts in the database, with their order and parents stored alongside. A damaged database table, a full database, or a failed update can make the write fail silently, so WordPress reloads the editor with the old data. Database faults are the least common cause, but they are the cause to check when every other fix fails, because no editor-side change can fix a table that will not accept writes.

Quick Checks

Two minutes before the deep fixes.

  • Click Save Menu once, wait for the page to reload, and read any notice at the top of the screen.
  • Check the Manage Locations tab to see which menu is assigned to each theme location.
  • Count the menu items — menus with more than about 50 items often hit the server input limit.
  • Check whether the menu ever saved correctly, and what changed since — a new plugin, a theme change, or a host move.
  • Check the live site in a private browser window, so your own browser cache cannot mislead you.
  • Think about what changed — did wordpress navigation menu not saving begin after an update, a new plugin, or a menu that grew much larger?

Diagnosing the Problem

SymptomCauseGo to Fix
Save button does nothing when clickedJavaScript error in the editorFix 12
Menu saves but the site shows the old menuCache serving the old headerFix 6
Some items save, others vanishServer input limit cutting the requestFix 5
Edits show in the dashboard, not on the siteWrong menu assigned to the locationFix 3
Menu items refuse to drag or expandPlugin script conflictFix 7
Save worked before a theme changeTheme location not supportedFix 8
No user can save any menuPermissions or database faultFix 11
Menu editor page shows errors or a blank areaDamaged menu data or database faultFix 13

Fix 1: Save the Menu Again and Watch for the Confirmation Notice

The first test is the simplest: save once, slowly, and watch what WordPress says. A successful save shows a notice at the top of the menu editor, and the page reloads with the new structure in place. Rushing the save — clicking twice, navigating away early, or saving while the page is still loading — can interrupt the request. One careful save, watched to the end, establishes whether saving works at all.

A hand clicking a save button on a laptop showing a website dashboard — wordpress navigation menu not saving fix guide
One slow, watched save tells you whether the editor works at all, before you change anything else.
  1. Open the dashboard and go to Appearance, then Menus.
  2. Select the menu you want to edit from the drop-down, and click Select.
  3. Make one small change, such as renaming one menu item.
  4. Click Save Menu once, and wait for the page to fully reload.
  5. Read the notice at the top of the screen — it should confirm the menu was updated.
  6. Check that your small change is still there after the reload.
  7. Open the live site in a new tab and check the change appears there too.
  • Clicking Save Menu twice in quick succession can send two overlapping requests, and the second can overwrite the first.
  • If the notice says the menu was updated but the change is gone, the fault is in the write or the display, and Fixes 3 to 6 apply.
  • If no notice appears and the page simply reloads, a script error is likely, and Fix 12 applies.
  • A single small change is the right test: if one item saves, the editor works, and the fault is size or content, not the save mechanism.

Fix 2: Clear the Browser Cache and Try a Different Browser

A stale browser cache can load an old copy of the menu editor’s scripts, so the editor misbehaves while the site itself is fine. Browser extensions, especially ad blockers and script blockers, can also interfere with the editor. Testing in a clean browser with no extensions rules out your own computer in minutes, before you touch the site.

  1. Open the menu editor in a private or incognito browser window, which loads no extensions and no cache.
  2. Sign in to the dashboard in the private window.
  3. Open Appearance, then Menus, and make one small change.
  4. Click Save Menu and check whether the change survives the reload.
  5. If it saves in the private window, clear the cache and cookies in your normal browser.
  6. Disable browser extensions one at a time in your normal browser, testing the save after each.
  7. If the private window also fails, the fault is on the site, and Fixes 3 onwards apply.
  • Private windows do not share cache or extensions with normal windows, which is what makes them a clean test.
  • A different browser entirely — for example, Firefox if you normally use Chrome — is an even cleaner test.
  • Clearing the browser cache signs you out of some sites, so have your WordPress password ready.
  • When wordpress navigation menu not saving affects only one browser, the browser is the cause, and the site needs no changes at all.

Fix 3: Check the Menu Is Assigned to the Right Theme Location

The Manage Locations tab shows which menu appears in each theme location. If the location shows a different menu from the one you edited, your edits are saved but invisible on the site. This mismatch is common after theme changes, imports, or working with several similar menus. Assigning the right menu takes seconds and often ends the whole fault.

  1. In the dashboard, go to Appearance, then Menus.
  2. Click the Manage Locations tab at the top of the page.
  3. Read which menu is assigned to each location, especially the primary or main location.
  4. If the location shows the wrong menu, or — Select a Menu —, choose the menu you edited.
  5. Click Save Changes at the bottom of the Manage Locations tab.
  6. Open the live site in a new tab and check the correct menu now appears.
  7. If the location list is empty, the theme may not support menu locations — check Fix 8.
  • The Manage Locations save is separate from the menu editor save — both must be done.
  • Some themes name locations unclearly, so check the theme’s documentation if the location names confuse you.
  • After assigning the menu, clear the cache with Fix 6 before judging the result, so a cached header cannot mislead you.
  • Renaming menus clearly — “Main Menu”, “Footer Menu”, “Mobile Menu” — prevents this mix-up in future.

Fix 4: Save Small Changes in Batches Instead of One Large Save

A large menu save sends hundreds of fields in one request, and servers, security plugins, and proxies can all choke on very large requests. Saving in small batches — a few items at a time — keeps each request small and reliable, and it shows exactly which change breaks the save. It is slower, but it works on menus that refuse to save all at once.

  1. Open the menu editor and note the full list of changes you want to make.
  2. Make only the first three or four changes, such as adding three items.
  3. Click Save Menu and confirm the changes survive the reload.
  4. Make the next three or four changes, and save again.
  5. Continue in small batches until all changes are saved.
  6. If one batch fails, split it further — save one item at a time until the failing item is found.
  7. Remove or recreate the failing item, which may have a broken link or a damaged setting.
  • A single item with a very long custom link, or a link to a deleted page, can break a whole batch — the batch method finds it.
  • Saving in batches is a workaround, not a cure: if large saves always fail, Fix 5 raises the limit properly.
  • Keep a note of which items are saved, so a failed batch does not leave you unsure what is done.
  • When wordpress navigation menu not saving affects only large saves, the request size is the cause, and batching proves it.

Fix 5: Raise the PHP Input Limit for Large Menus

The max_input_vars setting caps how many fields the server accepts in one request, and the default of 1000 is too low for menus with many items. Each menu item uses roughly a dozen fields, so a menu of 80 items can exceed the cap. Raising the limit to 3000 or 5000 lets large menus save in one request. The change is made in the hosting settings, and your host can apply it if you cannot.

  1. Open Tools, then Site Health, then Info, and expand the Server section to read the current max_input_vars value.
  2. If the value is 1000 or lower, and the menu is large, the limit is very likely the cause.
  3. In your hosting control panel, look for PHP settings, PHP options, or MultiPHP INI Editor.
  4. Raise max_input_vars to 3000, or 5000 for a very large menu.
  5. Save the PHP setting, and wait a minute for the change to take effect.
  6. Return to the menu editor, make the full set of changes, and click Save Menu.
  7. If the host panel has no PHP setting, contact the host and ask them to raise max_input_vars to 3000.
  • Do not edit server files by hand unless you are confident — the hosting panel or the host’s support team is the safe route.
  • Raising the limit affects the whole site, and it also helps other large forms, such as big settings pages.
  • After raising the limit, recheck Site Health to confirm the new value is active before testing the save.
  • A menu that saves in batches but not all at once, and then saves fully after this change, proves the limit was the cause.

Fix 6: Clear the Site Cache, Server Cache and CDN Cache

Caches store the old header, so a saved menu can look unsaved for hours. WordPress sites often have three cache layers at once: a caching plugin, a server cache run by the host, and a content delivery network cache. Clearing only one layer leaves the others serving the old menu. Clear all three, then check the site in a private window.

A laptop and phone showing the same website with a fresh menu — wordpress navigation menu not saving fix guide
A saved menu can stay hidden behind three layers of cache — clear them all before judging the result.
  1. In the dashboard, find the caching plugin’s menu — usually in the top toolbar — and choose Purge All or Clear Cache.
  2. Open your hosting control panel and clear the server cache, if the host provides one.
  3. If the site uses a CDN, open the CDN dashboard and purge the cache for the homepage and the header pages.
  4. Clear your own browser cache, or open the site in a private window.
  5. Open the live site and check whether the saved menu now appears.
  6. If the menu appears, the save was working all along, and the cache was hiding it.
  7. Set the caching plugin to clear the cache automatically when a menu is saved, if it offers that option.
  • Purge, not just clear one page: the menu appears in the header of every page, so the whole cache must go.
  • Some hosts cache at the server level with no dashboard button — ask the host to clear it if you cannot find the control.
  • If cached content keeps returning, our guide to WordPress cache not clearing covers the deeper cache layers.
  • After clearing, wait a minute before checking, because the first visit after a purge rebuilds the cache slowly.

Fix 7: Test for a Plugin Conflict in Troubleshooting Mode

A plugin conflict is the most common cause of a menu editor that stops working suddenly. The Health Check plugin’s Troubleshooting Mode disables all plugins for your session only, while visitors keep seeing the normal site. Testing the save in that mode proves whether a plugin is the cause, without disturbing the live site at all.

  1. Install and activate the free Health Check & Troubleshooting plugin from WordPress.org.
  2. Go to Tools, then Site Health, then Troubleshooting, and click Enable Troubleshooting Mode.
  3. Open Appearance, then Menus, and make one small change.
  4. Click Save Menu and check whether the change survives the reload.
  5. If the save works, re-enable plugins one at a time, testing the save after each, until the culprit is found.
  6. Keep the culprit plugin disabled, or replace it, and report the conflict to its developer.
  7. Click Disable Troubleshooting Mode to restore the normal site.
  • Troubleshooting Mode affects only your logged-in session — visitors see the site normally throughout the test.
  • Test the most recently installed or updated plugins first, because the newest change is the most likely cause.
  • Admin-enhancement, menu, and security plugins are the usual suspects for menu-editor conflicts.
  • For a full conflict-testing method, our guide to WordPress plugin conflict fix covers the step-by-step process.

Fix 8: Switch Briefly to a Default Theme

The active theme controls the menu locations and can load scripts that affect the menu editor. A theme fault can break saving, hide locations, or display the wrong menu. Switching briefly to a default theme such as Twenty Twenty-Five rules the theme out. The test changes the site’s appearance for a few minutes, so do it at a quiet time, and switch back promptly.

  1. Note the current theme name, so you can switch back to it exactly.
  2. Go to Appearance, then Themes, and activate a default theme such as Twenty Twenty-Five.
  3. Open Appearance, then Menus, and make one small change.
  4. Click Save Menu and check whether the change survives the reload.
  5. Check the Manage Locations tab to see whether the default theme shows locations the old theme hid.
  6. Switch back to the original theme immediately after the test.
  7. If the save worked under the default theme, the original theme is the cause — update it, or ask its developer for a fix.
  • Switching themes does not delete menus, pages, or posts — it only changes the appearance and the available locations.
  • Menu assignments can shift when themes change, so recheck Manage Locations after switching back.
  • If the theme includes a custom header builder, the header may hold its own menu — check the theme’s header settings too.
  • Header and menu problems often travel together: our guide to Elementor sticky header not working covers header-side faults.

Fix 9: Save the Menu From the Customizer Instead

The Customizer offers a second menu editor, reached through Appearance, then Customize, then Menus. It saves through a different path from the main menu editor, and it shows a live preview of the result. When the main editor fails but the Customizer works, the fault is in the main editor’s scripts, and the Customizer becomes a reliable way to save while the editor fault is investigated.

  1. In the dashboard, go to Appearance, then Customize.
  2. Click Menus in the Customizer sidebar.
  3. Select the menu to edit, or create a new menu from the Customizer.
  4. Make the changes, watching the live preview update on the right.
  5. Click Publish at the top of the Customizer sidebar.
  6. Open the live site in a new tab and check the menu shows the changes.
  7. If the Customizer save works, keep using it while you investigate the main editor with Fixes 7 and 12.
  • The Customizer is not available in the same form on block themes — on those themes, use the Site Editor in Fix 10 instead.
  • Publishing in the Customizer saves the menu and the location assignment together.
  • If the Customizer also fails to save, the fault is deeper — the server limit, the database, or permissions — and Fixes 5, 11, and 13 apply.
  • A Customizer save that works proves the database accepts menu writes, which rules out the database cause.

Fix 10: Edit the Menu With the Navigation Block in the Site Editor

Block themes manage navigation through the Navigation block in the Site Editor, not through the classic Menus screen. On a block theme, the classic screen may be hidden, limited, or out of sync with the Navigation block, so edits made there never reach the site. Editing the Navigation block directly, in the template that displays it, is the correct path for block themes.

A notebook with a sketched website menu structure beside a laptop — wordpress navigation menu not saving fix guide
A menu rebuilt from scratch drops the damaged item that blocked every save.
  1. In the dashboard, go to Appearance, then Editor.
  2. Open the template part that holds the header, usually called Header.
  3. Click the Navigation block to select it, and check which menu it displays.
  4. Edit the menu items inside the block: add, remove, reorder, and nest items as needed.
  5. Click Save at the top right, and review the list of changes before confirming.
  6. Open the live site in a new tab and check the header menu shows the changes.
  7. If the Navigation block shows a different menu from the one you edited, switch the block to the correct menu in its settings.
  • The Site Editor saves templates and menus together, so review the change list carefully before confirming.
  • A Navigation block can hold its own menu, separate from any classic menu — check the block’s menu setting, not just its items.
  • If the Editor menu item is missing, the theme is a classic theme, and the classic Menus screen in Fix 1 is the right editor.
  • On hybrid themes, both editors exist, and they can disagree — pick one editor and use it consistently.

Fix 11: Check Your User Role Has Permission to Edit Menus

Menu editing needs the right capability, which administrators have by default. Editors, custom roles, and multisite users may lack it, and a role changed by a membership or user-management plugin can lose the capability silently. The editor may appear to work but refuse to save, or the Menus screen may be missing entirely. Checking the role takes a minute and explains saves that fail for one user but work for another.

  1. In the dashboard, go to Users, then All Users, and find your username.
  2. Check the Role column — it should say Administrator for full menu access.
  3. If the role is lower, ask an administrator to raise it, or to make the menu change for you.
  4. If you are an administrator and the save still fails, check for a role-editor plugin that may have changed capabilities.
  5. Temporarily disable any user-role or membership plugin, and test the save again.
  6. On a multisite network, check that the menu is being edited on the correct site, not the network dashboard.
  7. Test the save with a second administrator account, if one exists, to rule out an account-specific fault.
  • A role plugin can remove the menu capability from administrators too, so check the capability list, not just the role name.
  • Multisite super admins edit menus per site, not from the network admin — switch to the site dashboard first.
  • If only one user cannot save, the fault is in that user’s role or account, not in the site.
  • Never hand out administrator access casually to fix a menu fault — fix the role properly, and keep access limited.

Fix 12: Fix the JavaScript Error That Blocks the Save Button

The menu editor’s Save button, dragging, and item expansion all run on JavaScript. A JavaScript error from any plugin or theme script can halt the whole editor, leaving a button that does nothing when clicked. The browser console shows the error and names the file that caused it, which points straight at the culprit plugin or theme.

  1. Open the menu editor in Chrome or Firefox, and press F12 to open the developer tools.
  2. Click the Console tab, then reload the menu editor page.
  3. Look for red error messages, and note the file name shown on the right of each error.
  4. Make one small menu change and click Save Menu, watching for new errors in the console.
  5. If an error names a plugin file, disable that plugin and test the save again.
  6. If an error names the theme, switch to a default theme briefly, as in Fix 8, to confirm.
  7. If the console shows a jQuery error, check for a plugin loading its own outdated jQuery copy, and disable it.
  • Console errors that appear on every admin page are less useful than errors that appear only when you click Save — focus on the save-time errors.
  • Minification and combination plugins can merge scripts badly and create errors — pause script optimisation while testing.
  • When styles also fail to update, our guide to WordPress CSS changes not updating covers the caching and minification side.
  • A clean console with a still-failing save points away from JavaScript and towards the server limit or the database.

Fix 13: Check Site Health and Repair the Database Tables

Site Health reports database problems, failed updates, and missing requirements that can silently block saves. If a menu-related table is damaged, WordPress cannot write menu items reliably, and the editor reloads with old data. The built-in database repair, enabled briefly through a configuration setting, can fix damaged tables — but take a backup first, because repair changes the database directly.

A laptop showing a database health report beside a backup drive — wordpress navigation menu not saving fix guide
Site Health reports the database and server faults that silently block a save.
  1. Take a full backup of the site, including the database, before touching anything.
  2. Open Tools, then Site Health, and read the Status tab for critical issues.
  3. Expand the Info tab and check the Database section for errors or warnings.
  4. If Site Health reports a database problem, ask your host to check the database and repair the tables.
  5. Alternatively, add the repair setting to wp-config.php only if you are confident editing it, run the repair, then remove the setting.
  6. After any repair, open the menu editor, make one small change, and click Save Menu.
  7. Remove the repair setting if you added it, and keep the backup until the menu saves reliably.
  • Never run a database repair without a backup — repair can discard damaged rows, and the backup is the only way back.
  • A full database, where the hosting quota is reached, also blocks writes — check the database size with the host.
  • If Site Health shows no database issue, the database is probably healthy, and the fault lies elsewhere.
  • Asking the host to repair is the safer path for most site owners, because the host can also check the database server itself.

Fix 14: Delete and Rebuild the Damaged Menu

A menu can carry damaged data: an item pointing at a deleted post, a corrupted parent link, or an item with broken settings that fails every save. When one menu refuses to save while a new test menu saves fine, the menu data itself is damaged. Deleting the menu and rebuilding it fresh, with the same items, removes the damaged data while keeping the same structure.

  1. Take a backup, and note the current menu structure — items, order, and submenu nesting — on paper or in a screenshot.
  2. Create a new test menu with two items, save it, and confirm the test menu saves correctly.
  3. If the test menu saves, the old menu’s data is the fault — proceed to rebuild it.
  4. In the menu editor, select the damaged menu and click Delete Menu at the bottom.
  5. Create a new menu with the same name, and add the items back in the noted order.
  6. Assign the new menu to the correct theme location on the Manage Locations tab.
  7. Save, clear the cache with Fix 6, and check the live site shows the rebuilt menu.
  • Deleting a menu deletes only the menu structure — pages, posts, and categories are untouched.
  • Rebuild in batches, saving every few items, so a single bad item is caught early rather than at the end.
  • If one item fails to add during the rebuild, that item’s target is the damaged part — recreate its page or use a fresh custom link.
  • When wordpress navigation menu not saving affects one menu but not a new test menu, this rebuild is the definitive fix.

Fix 15: Update WordPress, the Theme and Plugins, Then Re-Save

Outdated software carries known bugs, including menu-editor bugs fixed in later releases. An outdated theme can load old editor scripts, and an outdated plugin can conflict with the current WordPress version. Updating everything, then re-saving, clears the whole class of version-mismatch faults at once. Back up first, update in a quiet period, and test the save after each group of updates.

  1. Take a full backup of the site, including files and the database.
  2. Go to Dashboard, then Updates, and note what is available.
  3. Update WordPress core first, if an update is offered, and wait for it to finish.
  4. Update plugins next, in small groups, testing the menu save after each group.
  5. Update the active theme last, and recheck the menu locations after the theme update.
  6. Open the menu editor, make the full set of changes, and click Save Menu.
  7. Clear all caches with Fix 6, and check the live site in a private window.
  • Update on a staging copy first if the site is busy or earns income — updates can change appearance as well as fix bugs.
  • If an update breaks the menu editor further, the backup lets you roll back, and the update group that broke it names the culprit.
  • Keep WordPress, the theme, and plugins updated on a regular schedule afterwards, so version faults do not return.
  • A save that works after updating proves the fault was a fixed bug, and no deeper repair is needed.

What to Avoid

  • Do not keep clicking Save Menu repeatedly — overlapping save requests can overwrite each other and hide the real fault.
  • Do not edit the database directly unless you have a backup and know exactly what you are changing.
  • Do not install nulled or pirated themes and plugins — they can carry malware and break the editor in ways no fix can undo.
  • Do not raise server limits to extreme values without advice — a sensible limit fixes menus without weakening the server.
  • Do not delete a menu before noting its structure — rebuilding from memory loses submenu nesting and custom links.
  • Do not switch themes on a busy live site without warning — visitors see the changed appearance during the test.
  • Do not ignore the cache — a saved menu hidden behind cache looks exactly like a failed save, and leads to needless changes.

Frequently Asked Questions

Why is wordpress navigation menu not saving even though I click Save Menu?

Because the save request is failing silently somewhere between the button and the database. The usual causes are the server input limit on large menus, a plugin breaking the editor’s JavaScript, or a cache hiding a successful save. Work through Fix 1, Fix 5, Fix 6, and Fix 7: save once carefully, raise the input limit, clear every cache, and test for a plugin conflict. One of those four ends most cases.

Why does my menu save in the dashboard but not show on the live site?

Because the dashboard and the site can show different menus. Either the wrong menu is assigned to the theme location, or a cache is serving the old header. Check Manage Locations with Fix 3, then clear all cache layers with Fix 6, then check the site in a private window. If the menu still does not appear, the theme may not support the location, and Fix 8 applies.

How many menu items is too many for one menu?

There is no fixed number, because the limit is the server’s input field cap, not the item count. As a rough guide, menus above about 50 items often hit the default limit of 1000 input fields. If a large menu saves in batches but not all at once, the limit is the cause, and raising it with Fix 5 is the proper cure. Splitting a very large menu into a main menu and a footer menu also helps.

Can a plugin really stop a menu from saving?

Yes. The menu editor depends on JavaScript, and a plugin that loads a broken or conflicting script can stop the Save button, the dragging, and the item panels all at once. Troubleshooting Mode in Fix 7 proves it safely, because it disables plugins only for your session while visitors see the normal site. Menu, admin-enhancement, and security plugins are the most common culprits.

Should I edit the menu in the Customizer or the Menus screen?

Use whichever works reliably on your site, and use it consistently. The Menus screen suits classic themes and large menus, the Customizer suits quick edits with a live preview, and the Site Editor suits block themes. Mixing editors can cause confusion when one editor’s view of the menu disagrees with another’s, so pick one path per site and stick to it.

Will rebuilding the menu delete my pages?

No. Deleting a menu deletes only the menu structure — the list of links, their order, and their nesting. Pages, posts, categories, and media are untouched. Fix 14 rebuilds the same structure with fresh menu data, which removes whatever damaged item was blocking the save. Note the structure first, so the rebuild matches the original.

Conclusion

When wordpress navigation menu not saving wastes your edits, start with one careful save, then check the location assignment, the cache, and the menu size, and only then test plugins, themes, and the database. Most menus are fixed by the first six fixes, because the save is blocked by a limit, a cache, or a wrong assignment — not by damage. Finish by checking the live site in a private window after a cache clear, because a menu that survives a refresh on the live site is the proof the save truly works. Keep menus lean, keep software updated, and the editor will save first time, every time.

Helpful Official Resources

Leave a Reply

Your email address will not be published. Required fields are marked *