WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #33807


Ignore:
Timestamp:
09/10/2015 04:11:50 PM (8 years ago)
Author:
ocean90
Comment:

Hi ramymelegy, welcome to trac.

Thanks for your report. We're tracking this issue in #33423, it will be fixed with the next minor release.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33807

    • Property Status changed from new to closed
    • Property Resolution changed from to duplicate
    • Property Milestone changed from Awaiting Review to

  • Ticket #33807 – Description

    initial v1  
    55Step 1. Fix the actual issue by applying part of the patch in that ticket. It's a one liner. Open the wp-includes/taxonomy.php file, and go to line 4448. This is that line:
    66
     7
     8{{{
    79wp_schedule_single_event( 'wp_batch_split_terms', time() + MINUTE_IN_SECONDS );
     10}}}
     11
    812
    913The problem is that the arguments are reversed. Switch them, like so:
    1014
     15
     16{{{
    1117wp_schedule_single_event( time() + MINUTE_IN_SECONDS, 'wp_batch_split_terms' );
     18}}}
     19
    1220
    1321That will fix the underlying issue, but it won't stop the load. To do that, we're going to make a temporary mu-plugin.
    … …  
    1725Create a new file called "fix.php".
    1826
     27
     28{{{
    1929<?php
    2030function clear_bad_cron_entries() {
    … …  
    2737}
    2838clear_bad_cron_entries();
     39}}}
     40
    2941i want to inform you thats fix my problem and hope to upgrade soon to solve this problem
    3042regards