• Resolved harmoney

    (@harmoney)


    When WP CLI runs a wordpress command, it sets the max_execution_time to unlimited (or 0).

    CM Tooltip Glossary checks if the PHP setting is less than 300 seconds, setting it to that if needed. Unfortunately this incorrectly identifies unlimited execution times. This breaks our site’s search indexing of around 100,000 records, which we do using WP CLI explicitly to avoid timeout issues.

    Please revise the max_execution_time logic to handle unlimitted settings correctly. (Amusingly, the cminds_compatibility_check already correctly handles 0 values.)

    find wp-content/plugins/ -name '*.php' -print0 | xargs -0 grep max_execution_time | grep 300
    wp-content/plugins/enhanced-tooltipglossary/cm-tooltip-glossary.php:    if ( !ini_get( 'safe_mode' ) && !ini_get( 'max_execution_time' ) || ini_get( 'max_execution_time' ) < 300 ) {
    wp-content/plugins/enhanced-tooltipglossary/cm-tooltip-glossary.php:            @ini_set( 'max_execution_time', 300 );
    wp-content/plugins/enhanced-tooltipglossary/package/cminds-free.php:                        <td><?php if ($max_execution_time != 0 && $max_execution_time < 300): ?>
    wp-content/plugins/enhanced-tooltipglossary/package/cminds-free.php:                <?php if ($max_execution_time != 0 && $max_execution_time < 300): ?>
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘CM Tooltip Glossary breaks WP CLI unlimited max_execution_time’ is closed to new replies.