• Resolved erdincyildiz

    (@erdincyildiz)


    Hi, after updating from 1.82 to 1.83 i got this error:

    éFatal error: Maximum execution time of 30 seconds exceeded in /var/www/vhosts/xxxxxxxxxxxxxx.com/httpdocs/wp-admin/includes/class-wp-filesystem-direct.php on line 478

    Whwn i downgraded to 1.82, 1.81 they didn’t work any more either.

    So i downgraded to 1.72 now, which works for now.

    Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Anonymous User 16850768

    (@anonymized-16850768)

    I’m sorry that you’re experiencing this issue, @erdincyildiz. In your case, is this resolved if you increase your max execution time, like to 60 or 180?

    If no, would it be possible to receive a screenshot of your Cache Enabler settings in addition to your Site Health Info? This be obtained by going to the WordPress dashboard > Tools > Site Health > Info > Copy site info to clipboard. (It can be provided privately through our contact form while referencing this thread if you’d prefer.)

    Thread Starter erdincyildiz

    (@erdincyildiz)

    Hi Corey,
    I deleted the plugin yesterday with my error_log file and the last entry that was in the wp config.php. Before that i had the same issue like some others that my wp config.php was emtied (clean).
    Had a 500 error on server side as well as site domain.
    Hosting provider helped me to enter server dashboard, even though i had the time to disable cache enabler thrue files management (kinda ftp).

    So i restored wp config thru backup.

    Today i gave it an other shot with 1.83v, ?t’s working for now but right after adding the plugin i have a new error_log file with 12,4 mb increasing half a mb every 1 hour.

    I set max execution time to 60 and then to 120 and then back to 60 as you suggested.

    The site health info i sent to your contact form referring to this link.

    And for the screenshot of cache enabler settings, totally clean (blank) nothing set, no execution time of cache, no minify, no mobile cache, seperate webp chache. Just e few cookies for wc and loggedin users.

    Mean while error_log has increased 200 more kb.

    Thank you.

    Anonymous User 16850768

    (@anonymized-16850768)

    Following up to see if this issue has been resolved for you when upgrading to version 1.8.4 after what we previously discussed.

    Thread Starter erdincyildiz

    (@erdincyildiz)

    Hi Corey, yes everything works fine. No error_log from cache enabler.
    Thank you.

    Anonymous User 16850768

    (@anonymized-16850768)

    Great! I’m glad to hear that.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Issue with v1.83’ is closed to new replies.