Date: Wed, 21 Jul 2010 09:29:07 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Yuri" <yuri@rawbw.com> Cc: ports@FreeBSD.org, Remko Lodder <remko@elvandar.org> Subject: Re: Wordpress outputs an empty page after ports upgrade Message-ID: <5C6C602BEEED46D5A71D5E13B18D9A2B@multiplay.co.uk> References: <4C4416A7.3060308@rawbw.com><A7B70092-48B6-4DBD-B0B4-86B2C03F8892@elvandar.org><4C45E262.40702@rawbw.com><2BF3C2F7-314C-432A-86E6-D743E5FBF983@elvandar.org><4C46013F.1080301@rawbw.com><5EECDB8B-326A-4A88-8E10-C0A6DEAF6937@elvandar.org> <4C461470.4040407@rawbw.com> <C38388693B604EFDAAB2A5EC375C074C@multiplay.co.uk> <4C46241E.5080806@rawbw.com> <4A7D65A93CB94C118AA5C0EAB15415A3@multiplay.co.uk> <4C463377.2040600@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Yuri" <yuri@rawbw.com> > 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'm sorry but your wrong, as you can clearly see from the port Makefile. Yes /usr/ports/UPDATING can be helpful but in this case the warning is presented by the pre-everything target which you will likely miss if your using portupgrade. All portupgrade does is manage the process of uninstalling the old version and installing the new version. So its generally fine for binary only packages but for those that include data which needs special handling on upgrade such as wordpress, perl, mysql etc you still need to do those processes manually. >> 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). Absolutely not, ALWAYS backup your data before each upgrade, its the only way to be sure you don't loose things if something goes wrong. In addition be especially careful with major version upgrades like 2.9 -> 3.0 as they often have additional caveats. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5C6C602BEEED46D5A71D5E13B18D9A2B>