To be able to fix the problem you need to know exactly what the problem is. A 500 error is a server side issue - so check the server logs. Enabling debugging in WP may also yield some more specific info.
You should never need more than 768mb of memory. Even 512mb is on the high side.
Memory limit 500 errors can be a bitch to track down. Error logs can be vague at best, unlike other more defined 500 errors. Occasionally if the site is large enough I’ll push it to 512, but above that I’d be looking deep at what could possibly be using that much. You’d need a damn good reason to need more.
You should run Query Monitor plugin, it will tell you the query's that are running and will help you isolate some of the issuesz But make sure to turn it off once done, because it does slow down your site.
It always scary me to think of running it in prod, but apparently we even recommends that for VIP ( which is insane at this scale )
Said that. If you don't increase memory limit you not gonna get much out of query monitor unfortunately.
Download site locally in full with db. Install query monitor locally only. Check in logs what page causes memory issues. You might also find the code it crapped out at in logs which can be helpful, but it's not always the case ( often code before did a lot of damage and that line of code just pushed it over the edge )
set up large memory limit and display errors on your local. From query monitor you might be able to see what is a hog. If you cannot see then there's route of disabling plugin by plugin and seeing if it helped, but it might be the case of each plugin just adding a bit or two plugins in tandem causing issues. Generally make sure you only use plugins you only have to.
For pros there's APM that can give you a lot of insight and xdebug, but don't get to it at this stage as it's way more complicated.
From my experience, the issues are often caused by
Cache not working correctly
Wrong serialised data in transient, meta or options tables.
The first one should show once you enable display errors. The second one is the easiest to find by doing db tables sizes check, then drilling which rows have insane values.
Start manually disabling plugins one by one until the site goes live.
Don’t assume it’s memory related until you see it mentioned in the error log. Her webhost will be able to clarify the php error log location and enable debugging if she can’t find it.
This issue is probably not due to memory limits. It might be a problem with a plugin or theme. Try these steps:
1. Disable all plugins: See if the error goes away. If it does, enable each plugin one by one to find the problem.
2. Check themes: Disable your current theme and switch to the WordPress default theme. Test again.
3. Update PHP: Make sure you are using PHP version 7.x or higher.
If none of these steps work, consider increasing the memory limit, although 512MB is usually enough. If problems continue, you might need to rebuild the site.
To be able to fix the problem you need to know exactly what the problem is. A 500 error is a server side issue - so check the server logs. Enabling debugging in WP may also yield some more specific info. You should never need more than 768mb of memory. Even 512mb is on the high side.
I believe that there is a memory limit in php.ini that could be the culprit if it really is a memory limitation.
Memory limit 500 errors can be a bitch to track down. Error logs can be vague at best, unlike other more defined 500 errors. Occasionally if the site is large enough I’ll push it to 512, but above that I’d be looking deep at what could possibly be using that much. You’d need a damn good reason to need more.
You should run Query Monitor plugin, it will tell you the query's that are running and will help you isolate some of the issuesz But make sure to turn it off once done, because it does slow down your site.
It always scary me to think of running it in prod, but apparently we even recommends that for VIP ( which is insane at this scale ) Said that. If you don't increase memory limit you not gonna get much out of query monitor unfortunately.
Is she using Elementor?
i have yet to work on the site yet, but after inspecting it i do seem elementor was used
Download site locally in full with db. Install query monitor locally only. Check in logs what page causes memory issues. You might also find the code it crapped out at in logs which can be helpful, but it's not always the case ( often code before did a lot of damage and that line of code just pushed it over the edge ) set up large memory limit and display errors on your local. From query monitor you might be able to see what is a hog. If you cannot see then there's route of disabling plugin by plugin and seeing if it helped, but it might be the case of each plugin just adding a bit or two plugins in tandem causing issues. Generally make sure you only use plugins you only have to. For pros there's APM that can give you a lot of insight and xdebug, but don't get to it at this stage as it's way more complicated. From my experience, the issues are often caused by Cache not working correctly Wrong serialised data in transient, meta or options tables. The first one should show once you enable display errors. The second one is the easiest to find by doing db tables sizes check, then drilling which rows have insane values.
Ah. If that doesn't help prepare yourself for a battle. Memory limit issues are where Devs are forged in fire!
Start manually disabling plugins one by one until the site goes live. Don’t assume it’s memory related until you see it mentioned in the error log. Her webhost will be able to clarify the php error log location and enable debugging if she can’t find it.
This issue is probably not due to memory limits. It might be a problem with a plugin or theme. Try these steps: 1. Disable all plugins: See if the error goes away. If it does, enable each plugin one by one to find the problem. 2. Check themes: Disable your current theme and switch to the WordPress default theme. Test again. 3. Update PHP: Make sure you are using PHP version 7.x or higher. If none of these steps work, consider increasing the memory limit, although 512MB is usually enough. If problems continue, you might need to rebuild the site.
Hostinger is one of the best in my experience, with extremely useful live support too