2013-07-03 22:58, Yves-Alexis Perez skrev:
> On mer., 2013-07-03 at 10:25 +0200, Paul Dreik wrote:
>> Notice: add_option was called with an argument that
>> is <strong>deprecated</strong>
>> since version 2.3 with no alternative available. in
>> /usr/share/wordpress/wp-includes/functions.php on line 2927
>> (repeated three times)
>
> My guess would be a plugin/theme not compatible with recent (post 2.3)
> wordpress. Do you have something like that installed?
No plugins but a theme that was modified from the earlier Debian
version. I am not sure that was the problem. I now have the site up
again. This is how I did it:
I switched to an unmodified upstream release (3.5.2, same as the current
Debian squeeze version). The same problem as earlier persisted. I turned
on mysql debugging and it looked like wordpress tried to prepare or try
to update the databases. I then tried logging in through $URL/wp-admin/
and I finally got some output. It told me it needed to upgrade the
database, which I was able to do without problems. Then things started
working as expected, and the story could have been over.
However, I prefer to run the debian package rather than upstream sources
(to get security updates etc. although I may have second thoughts about
that right now....). Therefore I switched back to the debian packages
version using a separate configuration in apache. As part of the earlier
trouble shooting, I had removed the themes folder. So now when I used
the Debian version, on the database that had been updated by the
upstream package, the page showed up, although without a theme. (This
was not the case earlier, so the removed themes folder was NOT the
solution.)
So, it seems like upgrading to a new version requires logging in to the
admin section to get it working properly. I assume this is also thye
case for the debian packaged version. I think it is really unfriendly of
wordpress to not give any output at all in this situation, not even when
enabling debugging. Maybe most people update through the web interface
rather than the distributions package updates and never get such problems.
According to the documentation at
http://codex.wordpress.org/Updating_WordPress#Step_2:_Update_your_installation
updating the database through the web interface is the right thing to
do. I do not think it would hurt to mention it among the other news
displayed when updating the package. People run debian stable for a
reason, and security updates that bump the version should in my opinion
be careful about breaking existing installations. I hope I contributed
instead of only complaining by troubleshooting and reporting my findings.
>>
>> Notice: Undefined index: HTTP_X_FORWARDED_PROTO in
>> /usr/share/wordpress/wp-config.php on line 56
>
> For this one I'm not so sure, but double checking the previous item
> should at least help.
This problem is unrelated to the problems I had and persists also in the
new version (upstream or not). It is solved by the attached patch.
thanks for your work with packaging wordpress!
paul
--- wp-config.php.orig 2013-07-04 12:45:14.026201299 +0200
+++ wp-config.php 2013-07-04 12:46:00.043700665 +0200
@@ -53,8 +53,10 @@
$table_prefix = 'wp_';
}
-if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https')
- $_SERVER['HTTPS'] = 'on';
+if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) &&
+ $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') {
+ $_SERVER['HTTPS'] = 'on';
+}
require_once(ABSPATH . 'wp-settings.php');
?>
