WordPress4.6 has come.

   Actually, I failed once. My Web Browser status bar told ‘done’, but the progressing page showed only two lines. Besides, the update marker didn’t have gone. So I tried again and had ‘Another update is currently in progress’.

   I accessed via FTP but couldn’t find .maintenance file. I looked for a solution on the internet and reached ‘Get rid of Another update is currently in progress’.

   I went to my WordPress database and deleted a record with option_name = ‘core_updater.lock’ from my wp_options table. It worked. My update was complete. Now, I have WordPress4.6.

   One of new features for Developers is ‘HTTP API internal changes’. Is it excellent? I don’t know because I’m not a developer but I was surprised with a lot of new files under /wp-includes/Requests.

HTTP API in 4.6

   I updated phpMyAdmin to 4.6.4 at this opportunity. The config.sample.inc.php of 4.6.4 is different from older ones in two places.

  1. The bold characters were added.
    /**
    * This is needed for cookie based authentication to encrypt password in
    * cookie. Needs to be 32 chars long.
    */
    $cfg[‘blowfish_secret’] = ”; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */
     
    If your setting chars are less than 32 long, you’ll have ‘The secret passphrase in configuration (blowfish_secret) is too short.’
  2. The following lines were deleted.
    /* Contrib / Swekey authentication */
    // $cfg[‘Servers’][$i][‘auth_swekey_config’] = ‘/etc/swekey-pma.conf’;

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.