- Install SureFeedback & Addons
- Update SureFeedback
- Main Site Or Dedicated Installation?
- Caching & SureFeedback
- Dashboard Shortcode
- Project Shortcode (Below 3.1.x)
- Project Shortcode
- Hosting
- Cloudways Compatibility
- Activate SureFeedback License
- Subscribed Projects Shortcode (Below 3.1.x)
- Customization Settings
- Emails
- Permissions Cheatsheet
- Slack Integration
- Export Comments in PDF / CSV
- Known Issues
- Increasing WordPress Memory Limit
- WPEngine Cache Exclusion
- Litespeed Caching
- Emails Not Sending
- Flywheel Compatibility
- Debugging
- Varnish Caching
- Gridpane Compatibility
- Chrome Incognito: Session Expired Notice
- Breeze Compatibility
- W3 Total Cache Compatibility
- Website Comments Not working
- Swift Performance Caching
- Flywheel Cache Exclusion
- WPRocket Compatiblity
- Manage Licenses
- Generate Invoice
- Download Failed: Unauthorized
- Translate SureFeedback
- Client & Colleague Accounts
- Provide Project Access
- SureFeedback On External Site
- WPML For Multilingual Sites
- Automating SureFeedback Workflows With SureTriggers
Increasing the WordPress Memory Limit
1) Increase memory in your config file.
Locate your wp-config.php file. This file is located in the root of your WordPress installation. Edit the file and enter something like:
define('WP_MEMORY_LIMIT', '128M');
It’s important to set WordPress memory because WordPress memory can be different from the server. You need to set this regardless of server memory settings
2) Increase memory in your php.ini file
If you have access to your PHP.ini file, change the line in PHP.ini. If your line shows 32M try 64M, 96M or 128M:
memory_limit = 96M;
Maximum amount of memory a script may consume (96MB)
3) Increase memory in your .htaccess file
If you don’t have access to PHP.ini try adding this to a .htaccess file:
php_value memory_limit 96M
4) Talk to your host
If none of the above works then talk to your host. They should be able to help you increase your memory limit.
We don't respond to the article feedback, we use it to improve our support content.