Thread: need help in this error

Just install bulk delete plugin, when i active it show error :

Code:

Fatal error:  Allowed memory size of 134217728 bytes exhausted  (tried to allocate 71 bytes) in public_html/wp-includes/taxonomy.php  on line 1992

when i try to edit taxonomy.php at line 1992 but some how i fail to understand the code work

anyone can help ?

bold is line 1992 :

Code:

 * @param string $taxonomy Optional. Update Term to this taxonomy in cache
 */
function update_term_cache($terms, $taxonomy = '') {
    foreach ( (array) $terms as $term ) {
        $term_taxonomy = $taxonomy;
        if ( empty($term_taxonomy) )
            $term_taxonomy = $term->taxonomy;

        wp_cache_add($term->term_id, $term, $term_taxonomy);
    }
}

thanks

Hi,

Is it a server issue? I had errors on one of my sites and the host needed to do something to the server. Because how it was set on his end.

Sami

Originally Posted by Sami4u

Hi,

Is it a server issue? I had errors on one of my sites and the host needed to do something to the server. Because how it was set on his end.

Sami

not sure high possible

you have used all your ram tell your host to higher your memory

Originally Posted by haynes11

you have used all your ram tell your host to higher your memory

thanks ... i going to move to dedi soon (lazy to do now )

Hi All,

that's not exactly RAM issue.

that's the error you encounter when PHP needs more memory to perform the task that what is currently allocated.

there is a setting in your php.ini which can be changed

refer

Solve PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried… | PHP programming | Tech-Recipes

Increase PHP allowed memory size limits | Open Data

Note : your current memory size is set to 128 MB.

no in short this can be checked without switching to Dedicated hosting.

yes but essentialy that is a ram issue your host has a set limit of how much ram you can use even if you have a whole dedi to yourself you can face this problem

You should contact the support because this is not a WP problem but a problem on server level.