BeTheme fix
BeBuilder Not Loading or Not Saving? How to Fix It in BeTheme
BeBuilder, the editor BeTheme used to call Muffin Builder, keeps each page's layout in custom fields and sends the whole thing back to the server every time you save. When it hangs, goes blank or loses your changes, the page your visitors see is almost always fine. What failed is the trip between your browser and the server, and BeTheme has a screen that shows where.
- [14:02:11] POST /wp-admin/admin-ajax.php
- Failed to load resource: 403 (Forbidden)
- PHP Warning: Unknown: Input variables exceeded 1000.
- To increase the limit change max_input_vars in php.ini.
- memory_limit 256M · max_execution_time 30
What you are seeing
- The editor stays on its loading screen and never shows the page
- You click Update, the button spins and nothing is saved
- A long page saves with its lower sections missing
- A 403 error appears when you save a section containing embedded code
- The BeBuilder panel is absent from the page editor altogether
Why it happens on BeTheme
Most common first.
- 1
max_input_vars set too low for a long page
Every section, wrap and item on a BeBuilder page becomes a set of fields sent to the server on save. PHP's default cap is 1,000 input variables, and it discards the rest without complaint. That is why the bottom of a long page disappears while the top saves normally. Muffin Group's own guidance asks for a far higher figure.
- 2
A firewall reading your save as an attack
Wordfence, other security plugins and server rules such as ModSecurity inspect what the builder posts. A layout containing an iframe, a script or a long block of HTML can look hostile. The request is refused, often with a 403, and the builder waits for an answer that never comes.
- 3
Memory or execution time running out
Opening the visual builder loads the page, the builder interface and every active plugin in one request. On a low memory limit or a short execution time, that request dies partway and the screen stays blank.
- 4
Script optimization applied to the editor
A caching plugin that combines or defers JavaScript for logged-in users, or a CDN feature that rewrites scripts, can break the editor while the public site looks normal. BeBuilder needs its scripts in the order the theme sends them.
- 5
The builder switched off in Theme Options
BeTheme can hide BeBuilder for particular user roles, or for everyone, from its Theme Options. If the builder is missing only for editors, or vanished after someone tidied the settings, it was disabled and not broken.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Confirm the live page, then back up
Open the page in a private window. If visitors still see it, your content is safe and only the editor has failed. Take a full backup before changing server settings. If the builder opens at all, click Save revision so BeBuilder holds a restore point of its own.
- 2
Read BeTheme's System Status
Go to BeTheme, Dashboard, System Status. It lists the server values the theme needs and marks the ones that fall short. Write down max_input_vars, the memory limit and the max execution time before touching anything.
- 3
Raise the three limits at the host
Muffin Group recommends max_input_vars between 5,000 and 10,000, at least 256 MB of memory and a max execution time of 180 seconds. Set them in your hosting panel's PHP settings, or ask the host to. Reload System Status to confirm the values took. Some servers have a master limit that overrides the local one.
- 4
Let the firewall learn the save
If you run Wordfence, put its firewall in Learning Mode, open the page, click Update, then switch protection back on. For a 403 with no security plugin installed, ask the host whether a ModSecurity rule fired on admin-ajax.php. Have that one rule excepted. Do not disable the firewall.
- 5
Rule out caches and other plugins
Purge your caching plugin and turn off JavaScript combining and deferral for logged-in users. If the builder still hangs, press F12, open the Console tab and read the first red line while the editor loads. On a staging copy, deactivate plugins in batches until BeBuilder opens.
- 6
Check the builder is enabled for your role
If BeBuilder is simply missing, look in BeTheme, Theme Options, Global, Advanced for the setting that controls builder visibility by user role. In the WordPress editor, open the three-dot menu at the top right, choose its options or preferences entry and make sure Page Options is ticked.
Keep it from coming back
- Recheck System Status after any hosting move or PHP change
- Split very long pages instead of stacking one more section onto them
- Exclude logged-in users from script optimization in your caching plugin
- Save a BeBuilder revision before any large edit
The permanent fix
A faster Next.js build, with a CMS made for your business
If BeBuilder stalls every time the host changes PHP or a security rule updates, your editing depends on a chain you do not control: server limits, a firewall, a builder and a page that keeps growing. A Next.js build with a custom CMS replaces that chain with an editor made of the fields your business actually changes, where saving a page is a small, plain request. It is worth weighing once editing has become the task everyone avoids.
| On BeTheme today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your BeTheme site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Not from the editor failing. The layout sits in the database as custom fields on the page, and the published version keeps displaying. The real risk is a partial save on a server with a low input limit, which is why you fix the limit before saving a long page again.
Muffin Group's guidance is 5,000 to 10,000, toward the top of that range for content-heavy pages. The PHP default of 1,000 is enough for a short page and not for a long one. BeTheme's System Status screen shows the value your server is using now.
A 403 means something refused the request before WordPress handled it. On BeTheme sites that is usually a security plugin's firewall or a ModSecurity rule at the host reacting to code inside the layout, such as an iframe or a script. Wordfence's Learning Mode or a rule exception at the host clears it.
It is the same system under a newer name. Muffin Builder was the theme's original editor inside the WordPress page screen, and the visual version that edits the page as visitors see it carries the BeBuilder name. Older tutorials that mention Muffin Builder still apply, including the server limits.
Keep reading
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.
- ServiceFixing Broken WebsitesSite down, hacked, or falling apart? We diagnose it fast, fix what's broken, and tell you straight how to keep it from happening again.