Wordpress outputs an empty page after ports upgrade
in [Ports]
|
From: Yuri on 20 Jul 2010 18:33 On 07/20/2010 15:15, Steven Hartland wrote: > Sounds like an upgrade issue, possibly a broken theme or missing > dependency. > > We're running WP 3 on FreeBSD here without problem, although we don't use > the port as I don't really see the need for WP tbh as its so easy to > install > anyway. port upgrades to the latest version automatically, this is the main benefit > First things to check, apache etc error logs, revert to the standard > theme > and go from there. No error messages in apache log. Theme is standard, has never been changed. > Saying it doesn't work doesn't help anyone help you ;-) You need to > detail > what you have an haven't tried. But I really don't have more info. I tried to see if it's going through the php code, it does go through headers: headers: X-Pingback -> http://localhost/wordpress/xmlrpc.php headers: Expires -> Wed, 11 Jan 1984 05:00:00 GMT headers: Last-Modified -> Tue, 20 Jul 2010 22:28:26 GMT headers: Cache-Control -> no-cache, must-revalidate, max-age=0 headers: Pragma -> no-cache headers: Content-Type -> text/html; charset=UTF-8 I get these printouts with my echo statements. Setting WP_DEBUG didn't change the behavior. Yuri _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Steven Hartland" on 20 Jul 2010 19:21 ----- Original Message ----- From: "Yuri" <yuri(a)rawbw.com> To: "Steven Hartland" <killing(a)multiplay.co.uk> Cc: "Remko Lodder" <remko(a)elvandar.org>; <ports(a)FreeBSD.org> Sent: Tuesday, July 20, 2010 11:33 PM Subject: Re: Wordpress outputs an empty page after ports upgrade > On 07/20/2010 15:15, Steven Hartland wrote: >> Sounds like an upgrade issue, possibly a broken theme or missing >> dependency. >> >> We're running WP 3 on FreeBSD here without problem, although we don't use >> the port as I don't really see the need for WP tbh as its so easy to >> install >> anyway. > > port upgrades to the latest version automatically, this is the main benefit 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. I've had peek at the workpress Makefile and it has the following in it which also indicates this is the case:- "If you want to upgrade, you must read upgrade document." So if you've just used the port to upgade, then this is likely your your problem. 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 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(a)multiplay.co.uk. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Yuri on 20 Jul 2010 19:38 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 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Steven Hartland" on 21 Jul 2010 04:29 ----- Original Message ----- From: "Yuri" <yuri(a)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(a)multiplay.co.uk. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
First
|
Prev
|
Pages: 1 2 3 Prev: portmaster packages and perl upgrade Next: Fonts in linux-thunderbird |