From owner-freebsd-ports@FreeBSD.ORG Tue Jul 20 23:38:36 2010 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AA411065703 for ; Tue, 20 Jul 2010 23:38:36 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 120258FC16 for ; Tue, 20 Jul 2010 23:38:35 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o6KNcV7x052552; Tue, 20 Jul 2010 16:38:32 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4C463377.2040600@rawbw.com> Date: Tue, 20 Jul 2010 16:38:31 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100708 Thunderbird/3.0.5 MIME-Version: 1.0 To: Steven Hartland References: <4C4416A7.3060308@rawbw.com><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> <4C46241E.5080806@rawbw.com> <4A7D65A93CB94C118AA5C0EAB15415A3@multiplay.co.uk> In-Reply-To: <4A7D65A93CB94C118AA5C0EAB15415A3@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Remko Lodder Subject: Re: Wordpress outputs an empty page after ports upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 23:38:36 -0000 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