• Resolved m4j4

    (@m4j4)


    Hi,
    I’m trying to update WP to 4.0 and it results in:

    Fatal error: Maximum execution time of 30 seconds exceeded in C:\xampp\htdocs\busybee\wp-admin\includes\class-wp-filesystem-direct.php on line 72

    Anyone knows what I shoud do?

    Cheers,
    M4j4

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator t-p

    (@t-p)

    Maximum execution time exceeded in

    You may receive a message such as “Maximum execution time of 30 seconds exceeded” or “Maximum execution time of 60 seconds exceeded”. This means that it is taking to longer for a process to complete and it is timing out. There are a number of ways to fix this error.
    Editing .htaccess

    Make sure you back up .htaccess before you edit it.

    Add the following line to .htaccess:
    php_value max_execution_time 60

    Editing php.ini

    Add the following to php.ini
    max_execution_time = 60 ;

    If you are unsure of how to make these changes, or if you are on shared hosting that prevents you from making them yourself, you should contact your hosting provider and ask them to increase your maximum execution time.

    Thread Starter m4j4

    (@m4j4)

    Hey, thanks. I’ll do what you suggest and let you know if I’ve made it.

    Thread Starter m4j4

    (@m4j4)

    Where in the.htacces should I put your line?

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /somename/
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /somename/index.php [L]
    </IfModule>

    # END WordPress

    Moderator t-p

    (@t-p)

    try placing after # END WordPress

    Thread Starter m4j4

    (@m4j4)

    It works! The update was sucessfull!!

    Thank you, thank you, thank you

    This tiny little trick of yours is a big treasure for me.

    M4j4

    Moderator t-p

    (@t-p)

    You are welcome ??

    Thread Starter m4j4

    (@m4j4)

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WP ne-click update results in fatal error’ is closed to new replies.