Cornerstone Critical Error When Saving One Specific Page – PHP Memory Exhausted (1024 MB)

Support
#1

Title: Cornerstone Critical Error When Saving One Specific Page – PHP Memory Exhausted (1024 MB)

Hi Themeco Support,

I’m experiencing an ongoing issue with Cornerstone on a WordPress website I’m currently developing for a restaurant client, and I’m hoping someone can help me identify what’s causing it.

Website: https://birdmanvic-ca.thekudosguide.ca/

This is a temporary development/staging URL. Once the website is completed, it will be launched on the restaurant’s permanent domain, birdmanvic.ca.

The issue:

Whenever I attempt to save changes to the Menu page in Cornerstone, I receive the following error:

“Failed to save – There has been a critical error on this website.”

I’ve checked the PHP error logs through my hosting provider, HostPapa, and found repeated fatal errors stating:

Allowed memory size of 1073741824 bytes exhausted

The website already has a PHP memory limit of 1024 MB (1 GB) , so I’m concerned about why saving a single page is consuming that much memory.

A few important things I’ve confirmed:

  • Every other page on the Birdman website saves normally through Cornerstone.
  • My other WordPress websites, which also use the Pro theme and Cornerstone, are saving normally.
  • The issue is isolated specifically to the Birdman Menu page.
  • I’ve been communicating with HostPapa support, but the issue remains unresolved.

How I’ve built the Menu page:

The Menu page is fairly long because the restaurant has several different menus, including Lunch + Late Night, Dinner, Happy Hour, Industry Hour, and Drinks.

However, I haven’t implemented anything particularly complicated from a technical standpoint.

The page primarily consists of standard Cornerstone sections containing text, images, and menu items.

The only slightly more technical feature is the navigation system I’ve created using Cornerstone’s built-in elements and reusable components.

I’ve created navigation buttons that link to corresponding sections further down the same page using standard anchor IDs.

For example, clicking the “Dinner” button automatically scrolls the visitor down to the Dinner menu section. Each individual menu also has its own category navigation, allowing visitors to jump directly to specific food or drink categories.

These navigation sections were created as reusable Cornerstone components to keep the design consistent and make editing easier.

There is no custom JavaScript or complicated functionality involved in these navigation buttons. They’re simply internal anchor links.

I’ve attached a screenshot showing the main navigation component and the page structure in Cornerstone.

What HostPapa has investigated:

I contacted HostPapa after discovering the PHP memory exhaustion errors.

Initially, they suggested the issue could be related to excessive background processes from the UpdraftPlus backup plugin on another WordPress installation within my hosting account.

I subsequently removed the old backup files and unnecessary plugins from that website, freeing up a significant amount of server storage.

However, this made no difference to the Birdman Menu page.

HostPapa later identified additional WordPress cron activity on another website and recommended further troubleshooting.

While I understand that server resource usage can affect performance, the fact that every other page on Birdman saves successfully makes me wonder whether the issue is specifically related to how Cornerstone is processing the Menu page.

My questions:

  1. Could having multiple reusable Cornerstone components on one page cause unusually high memory consumption during saving?
  2. Is there a known issue with saving particularly long pages containing numerous sections and components?
  3. Could there be corrupted or problematic Cornerstone page data causing the memory exhaustion?
  4. Is there a way to diagnose which element, component, or process is responsible without deleting or rebuilding the page?

I’ve spent considerable time designing and organizing this Menu page, so I’d really like to avoid having to rebuild it from scratch.

I’m happy to provide additional screenshots, PHP error logs, or temporary WordPress access through a secure support channel if needed.

Any guidance would be greatly appreciated. This issue has been preventing me from completing the website for several days now.

Thanks so much!

#2

Hey Casandra,

Thank you for the detailed write-up. I understand that saving the Menu page in Cornerstone fails with a critical error and your PHP log shows memory exhausted at 1 GB, while every other page saves normally. Please review the steps below. None of them require deleting or rebuilding the page.

To answer your questions briefly: a long page with several reusable Components is not, on its own, a known cause of this. I checked the Menu page on your staging site: it loads normally, and each navigation Component is placed once, directly on the page, with none nested inside another. When you save, Cornerstone renders the whole page to HTML on the server and saves that HTML, and other plugins then process it on save. On a page this long, a plugin hooked into that step is the most likely place for memory to run out.

Step 1: Quick Check

  • Confirm PHP version is 8.1+.
  • Confirm both Pro/X and Cornerstone are updated to the latest versions. Your site is currently on Pro 6.9.8 with its built-in Cornerstone 7.9.8.

Step 2: Troubleshooting

  1. Deactivate the third-party “Cornerstone” plugin – Your site has a WordPress.org plugin named “Cornerstone” by Archetyped active (it loads wp-content/plugins/cornerstone/js/lib.core.js). It is not our builder and is not needed: Pro already includes Cornerstone. Please go to Plugins, deactivate “Cornerstone” by Archetyped, and save the Menu page again. If you did not install it intentionally, you can delete it afterwards.
  2. Check the full error line and test for a plugin conflict – If saving still fails, please send us the complete fatal error line from the PHP log. After the memory message, it reads “in /path/to/file.php on line N”, and that file path shows whether the memory is used by Cornerstone or by another plugin. Then, on staging, temporarily deactivate all other plugins (SEO and caching plugins especially), save again, and reactivate them one at a time to find the conflict.
  3. Isolate on a copy – If it still fails with only Pro active, duplicate the Menu page and work only on the copy. Remove one menu section at a time (for example Drinks, then Happy Hour) and save after each. When the copy saves, the last section removed holds the cause. Your original page stays untouched.

Separately, the anchor ID drinks-more is currently used on two sections, so a link to it will always jump to the first one. Please give one of them a different ID.

Step 3: Recommended Resources

Step 4: If the issue persists
Please provide your System Info (WP Admin > Cornerstone > System Info), the full fatal error line from the PHP log, and any browser console errors shown when the save fails. If you would like us to look directly, please add temporary admin access in a secure note on this thread. Please do not post login details publicly.

We would be happy to double check your site if we can log in. You can create a secure note in your next reply with the following info:
– Link to your site
– WP login URL
– WP username
– WP password
– WP Administrator Role
– Confirmation that we can access and make changes to your site

To know how to create a secure note, please check this out: How The Forum Works

image

Best Regards.

#3

Hi Ruenel,

Thank you so much for taking the time to look into this and for your detailed response!

I followed your suggestion and first deactivated the unrelated Cornerstone plugin, but unfortunately, that didn’t resolve the saving issue.

I then started deactivating the other plugins individually to narrow down the cause, and I finally found the culprit! After deactivating Forminator , I was able to save the Menu page in Cornerstone without receiving the critical error.

I’m relieved to have finally figured out what was causing the issue, especially after spending several days troubleshooting it with my hosting provider.

I really appreciate your help and for pointing me in the right direction. Thanks again!

#4

You are most welcome, Casandra.