Wordpress outputs an empty page after ports upgrade

Yuri yuri at rawbw.com
Tue Jul 20 23:38:36 UTC 2010


On 07/20/2010 16:21, Steven Hartland wrote:
> I think you may have got the wrong end of the stick there. Ports can 
> be used
> to uninstall the old and install the new version yes, but I don't 
> believe it
> automates any of the upgrade process required for something like 
> wordpress
> for you.

No, look at ports-mgmt/portupgrade, it is capable of upgrading ports 
in-place quite happily in most cases. With the caveat that there might 
be some special steps that need to be taken not covered by port itself. 
This usually happens when dependencies split or being renamed or some 
other wild change that isn't covered by the standard process. But in the 
case of wordpress no special record has been placed into 
/usr/ports/UPDATING, which means that portupgrade should be sufficient.
> I'd suggest restoring you pre-upgrade backup of both files and db and 
> perform a
> manual upgrade as per the wordpress guide.
> http://codex.wordpress.org/Upgrading_WordPress

This is quite unpractical with many packages installed on the system. 
Also WP has an embedded DB update process that is activated 
automatically when you first run after system upgrade. This makes manual 
upgrade redundant (at least theoretically).

Yuri


More information about the freebsd-ports mailing list