You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: If hosting service is misconfigured and reports incorrect avail/total memory amount, search functions fail to execute and present results.
My host refuses to address this since the site essentially works.
Example searching for the string "export" inside my theme:
"Warning: The memory limit is about to be exceeded before the search has started, this could be an early indicator that your site may soon struggle as well, unfortunately this means the plugin is unable to perform any searches. Current memory consumption: 2353152 of 1 bytes"
However, if I edit line 88 in /includes/class-search.php from:
$memory_limit = ini_get( 'memory_limit' );
to something fixed like:
$memory_limit = '2G';
No more error and I get search results.
The text was updated successfully, but these errors were encountered:
Could you provide some more details on what the values are defined as on your environment? What is the value of ini_get( 'memory_limit' ) here? (Very interested since it appears to be interpreted as 1byte, which is not even enough to load up PHP)
Issue: If hosting service is misconfigured and reports incorrect avail/total memory amount, search functions fail to execute and present results.
My host refuses to address this since the site essentially works.
Example searching for the string "export" inside my theme:
"Warning: The memory limit is about to be exceeded before the search has started, this could be an early indicator that your site may soon struggle as well, unfortunately this means the plugin is unable to perform any searches. Current memory consumption: 2353152 of 1 bytes"
However, if I edit line 88 in /includes/class-search.php from:
$memory_limit = ini_get( 'memory_limit' );
to something fixed like:
$memory_limit = '2G';
No more error and I get search results.
The text was updated successfully, but these errors were encountered: