Solved Updating Wordpress

[balanga]

It seems that my version of Wordpress is out of date and an update is available. I'm told:-

You can update to WordPress 5.1–en_GB automatically:

I'm running this Wordpress in a jail under FreeNAS. How do I perform an update?

 

[SirDice]

You've been here long enough to know this: PC-BSD, FreeNAS, XigmaNAS, and all other FreeBSD Derivatives

 

[balanga]

I found an old installation of Wordpress (4.9.2) which is currently running under FreeBSD 12.0-RELEASE amd64 and it shows:-

WordPress 5.1.1 is available! Please update now.

When selecting 'Please update now' it runs wordpress/wp-admin/update-core.php but I get a HTTP ERROR 500

Any ideas if I am able to update Wordpress from within the program on FreeBSD? Or should I just install latest.tar.gz over the top of the current version?

 

[SirDice]

No, you should update using the package/port.

 

[balanga]

The problem is, I installed manually by extracting https://wordpress.org/latest.tar.gz to /usr/local/www/apache24/data so it is not listed as an installed pkg.

 

[msplsh]

1. Check your error logs to determine what the 500 is
2. Re-read the install instructions to see if how you installed it caused the problem
3. Fix the problem (and avoid it in the future)
4. Back up the site
5. Then if it doesn't upgrade, do the exact same thing you did to install it

 

[obsigna]

in the wp base directory, the subdirectory wp-content and the whole tree below must be writable by user www.
cd into the wp base dir and then execute # chown -R www wp-content.

Then try upgrading as WP admin again.

 

[balanga]

1. Check your error logs to determine what the 500 is

Not sure if I've identified the correct line as the log lines are very long, but this occurs near the begining of the line:-

PHP Fatal error: Uncaught Error: Call to undefined function gzinflate() in.
/usr/local/www/apache24/data/wordpress/wp-includes/class-requests.php:947

This is the function around line 947:-

// Finally fall back to straight gzinflate
if (false !== ($decompressed = @gzinflate($gzData))) {
     return $decompressed;
}

Can't see what it is complaining about...

 

[obsigna]

# pkg install php7x-zlib

And x should match your version of php

 

[balanga]

pkg info php71-zlib:-

php71-zlib-7.1.26
Name : php71-zlib
Version : 7.1.26
Installed on : Tue Feb 12 00:35:50 2019 GMT
Origin : archivers/php71-zlib
Architecture : FreeBSD:12:amd64
Prefix : /usr/local

but....

pkg info | grep 'php'

mod_php72-7.2.16 PHP Scripting Language
php71-bz2-7.1.26 The bz2 shared extension for php
php71-ctype-7.1.26 The ctype shared extension for php
php71-filter-7.1.26 The filter shared extension for php
php71-hash-7.1.26 The hash shared extension for php
php71-json-7.1.26 The json shared extension for php
php71-mbstring-7.1.26 The mbstring shared extension for php
php71-openssl-7.1.26 The openssl shared extension for php
php71-tokenizer-7.1.26 The tokenizer shared extension for php
php71-zip-7.1.26 The zip shared extension for php
php71-zlib-7.1.26 The zlib shared extension for php
php72-7.2.16 PHP Scripting Language
php72-mysqli-7.2.16 The mysqli shared extension for php
php72-session-7.2.16 The session shared extension for php

so looks like a bit of a mish mash. Should I update all the php71* to php72* ?

 

[SirDice]

Should I update all the php71* to php72* ?

Do you think you can mix and match 7.1 and 7.2 modules?

 

[balanga]

To be honest this was installed a year ago and I've only just come across the problem so it must have been working to some extent... I'll try installing all the php72* modules and see if the error goes away.

 

[balanga]

The original problem is now solved, but it appears that I need to have an ftp server to get the update, and since I don't have one I need to follow these instructions:-

https://wordpress.org/support/article/upgrading-wordpress-extended-instructions/