- Install SureFeedback & Addons
- Update SureFeedback
- Translate SureFeedback
- WPML For Multilingual Sites
- Main Site Or Dedicated Installation?
- Automating SureFeedback Workflows With OttoKit
- Manage Licenses
- Caching & SureFeedback
- Litespeed Caching
- Chrome Incognito: Session Expired Notice
- Gridpane Compatibility
- Breeze Compatibility
- W3 Total Cache Compatibility
- Download Failed: Unauthorized
- Flywheel Cache Exclusion
- Generate Invoice
- WPRocket Compatiblity
- Swift Performance Caching
- Debugging
- Varnish Caching
- Website Comments Not working
- Flywheel Compatibility
- Emails Not Sending
- WPEngine Cache Exclusion
- Increasing WordPress Memory Limit
- Client & Colleague Accounts
- Permissions Cheatsheet
- Slack Integration
- Export Comments in PDF / CSV
- Provide Project Access
- Hosting
- Subscribed Projects Shortcode (Below 3.1.x)
- Activate SureFeedback License
- Dashboard Shortcode
- Cloudways Compatibility
- Known Issues
- SureFeedback On External Site
- Emails
- Project Shortcode
- Customization Settings
- Project Shortcode (Below 3.1.x)
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.