You’re looking at the problem the wrong way. The error you’re seeing isn’t an error coming from WordPress, it’s a PHP error. Somehow, somewhere, something is limiting the memory limit to 96M, and it ain’t WordPress that’s doing it. Here’s the thing: WordPress can’t actually limit the memory on most servers. I know that it … Read more
update_field() is ACF function so I would guess the issue is with it. From quick look at source it calls get_field_object() and so on, so environment might not be sufficient for it to work correctly during import. There is no “half” state for native meta data, either it exists in database or it doesn’t. You … Read more
@Tal, Generally speaking you should only be using one caching plugin. WP Super Cache, W3 Total Cache, Hyper Cache and DB Cache Reloaded all drop files directly in your wp-content directory and they would conflict with each other and cause errors if you were using more than one. I would recommend using W3 Total Cache … Read more
The amount of memory that is allocated to PHP is insufficient. Add this to your wp-config.php file: define(‘WP_MEMORY_LIMIT’, ’64M’); If that doesn’t work, the chances are your host has this locked down and you can’t change it, in which case you either need to simplify your site, or move hosts.
The posts are still held in memory under WordPress’ cache mechanism (even though you replace $posts on every loop) – delete each one after operating on it: # do some echoing with the $post # wipe post from memory wp_cache_delete( $post->ID, ‘posts’ ); wp_cache_delete( $post->ID, ‘post_meta’ ); Pro tip: save some needless queries with no_found_rows … Read more
Just to put here the suggestion that came up after discussing the requirement on chat. Due to the complexity of user filtering/search required, the wordpress user data tables is not a very good place to store the user’s attributes. Instead it will make more sense to have a CPT and related taxonomies to store the … Read more
Using FTP, try increasing the memory for PHP and WordPress by editing the memory_limit line in your php.ini (if you have access to it) to 64M or 128M, which should be fine for non-multisite installs. memory_limit = 64M; If you can’t get to the php.ini file, add this line at the top of your .htaccess … Read more
It turns out that it was due to Query Monitor, a plugin that records info about each query. Every time update_post_meta ran, Query Monitor would store some data about the query, which eventually added up to be more than the server could handle. Running my example code on a default theme like Twenty Nineteen with … Read more
In your example, you are getting all the fields in the get_users call, but you are only really using the ID and display_name fields. So you can save some memory by forcing get_users to only get the fields you need. $users = get_users(array( ‘role’=>’s2member_level3’, ‘fields’=>array(‘ID’, ‘display_name’), )); That will help reduce your memory footprint.
CPU usage: AJAX and Heartbeat API on admin pages