Before asking for help please read "How to request help" by clicking on that tab above here."
Question Redirectionproblem after update
- Malte
- Topic Author
- Visitor
I've updated my old webtrees 1.2.3 to the current version (1.7.8= and now it is broken. I get an error to many redirects when I call my site. I've tried it with firefox, chrome and deleteed all cookies - no success.
In short to my updateprocess. I came from 1.2.3 and updated to 1.5.1 that works correct. Then I used the autoupdate function and now it is broken. When I now install the 1.5.1 again, it also didn't work. It seems thats now some settings are incorrect.
I also tried to call the index.php with the parameter ged=<ged-filename> but no success.
Any Ideas?
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
Did you set the "SERVER_URL" parameter? If so, try removing it (from the wt_site_setting_ table) from your database (e.g. using phpMyAdmin)
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- Malte
- Topic Author
- Visitor
As you suggested I deleted the tablerow and now I get this output:
If you like you can try it by yourown: stammbaum.hiapo.de
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- Malte
- Topic Author
- Visitor
5.3.2fisharebest wrote: Which version of PHP do you use on this server?
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
What happens if you delete this block of code?
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- Malte
- Topic Author
- Visitor
Here is the link to the modified file: stammbaum.hiapo.de/app/Theme.php.txt
And here is the reason:
But I found also this message from the morning. Maybe it is interesting:
Please Log in or Create an account to join the conversation.
- bertkoor
- Offline
- Platinum Member
- Greetings from Utrecht, Holland
That's a basic list for two themes (Clouds & webtrees) and not listing a lot of other stuff sitting in the same folders
But it looks like the access to the themes folder is too restrictive. Funny, because that folder structure was there in v1.3 as well.
stamboom.BertKoor.nl runs on webtrees v1.7.13
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
Although it claims to be 5.3.2, many Linux distributions (e.g. Debian, RedHat, Fedora, etc.) actually provide a custom build that contains patches from later versions - but still call it 5.3.2. Hence "5.3.2" can mean many things. For example, it may have fixes that were actually introduced in 5.3.9.
The code you removed was a workaround to support other versions of "5.3.2". FYI, according to the dev.webtrees.net/statistics.html there are 4 sites running successfully with PHP 5.3.2.
Fixing the code to work with your particular version of PHP would involve renaming the function Theme::theme - but this would break many other third-party modules and themes. I'm not going to do this.
You *really* should upgrade your server to a supported version of PHP - either 5.6 or 7.0
If you can't do this (you should!), then I suggest that you do not upgrade webtrees higher than 1.6 (this problematic code was introduced in 1.7.0).
Now, the upgrade to 1.7 would have made some database changes that cannot easily be downgraded to work with 1.6.
You will need a backup copy of your database from before the upgrade.
> But I found also this message from the morning. Maybe it is interesting:
That was me. Ignore it.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- Malte
- Topic Author
- Visitor
Yes, I know it.fisharebest wrote: You are using an ancient / obsolete version of PHP. (2010-04-04).
My intention was to upgrade to the last possible version on this server and then copy it to a new system with php 7 only. So after I read the documentation that 1.7.8 should work with my version 5.3.2 I decided to update it on my old server.fisharebest wrote: Although it claims to be 5.3.2, many Linux distributions (e.g. Debian, RedHat, Fedora, etc.) actually provide a custom build that contains patches from later versions - but still call it 5.3.2. Hence "5.3.2" can mean many things. For example, it may have fixes that were actually introduced in 5.3.9.
The code you removed was a workaround to support other versions of "5.3.2". FYI, according to the dev.webtrees.net/statistics.html there are 4 sites running successfully with PHP 5.3.2.
Fixing the code to work with your particular version of PHP would involve renaming the function Theme::theme - but this would break many other third-party modules and themes. I'm not going to do this.
You *really* should upgrade your server to a supported version of PHP - either 5.6 or 7.0
So my new plan is. Restore the backup to my old version 1.2.3 and update it to the first php 7 aware version. This version I will then copy to my new server.
Which is the first version with support for php 7?
fisharebest wrote: If you can't do this (you should!)
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
I can't remember. Sorry. Most likely the first version that was released after the release of PHP7.0
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- bertkoor
- Offline
- Platinum Member
- Greetings from Utrecht, Holland
fisharebest wrote: > Which is the first version with support for php 7?
I can't remember. Sorry. Most likely the first version that was released after the release of PHP7.0
PHP 7.0 was released about one year ago (December 2015)
It was also then that the first forum post mentioning PHP7 surfaces.
That topic links to a commit record in git which is first contained in the tag (and thus version) 1.7.3
Malte wrote: So my new plan is. Restore the backup to my old version 1.2.3 and update it to the first php 7 aware version.
Imho you could as well go directly to the latest version.
stamboom.BertKoor.nl runs on webtrees v1.7.13
Please Log in or Create an account to join the conversation.
- Malte
- Topic Author
- Visitor
Until now all things are working.
Thank you for your help.
Please Log in or Create an account to join the conversation.
- Andreas
- Offline
- Premium Member
Today I got the information that it would be good to update my php server version from 5.6.21 to the next actual one.
I did so and updated to php 7.0 but my page didn't work.
So I switched back to the old php version 5.6.21 and I deactivated all non webtrees modules in the admin panel.
Now I switched back to php 7.0 and the site worked fine, as well as the admin panel.
But when I tried to open the module admistration to switch on the deactivated modules I get only a white page.
What's the hell is blocking here ? Can you please give me a hint ?
Both MAUPILLÉ & RAUHUT families are using webtrees V2.1.18
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
check your webserver error logs
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- Andreas
- Offline
- Premium Member
[Sat Dec 31 09:49:05 2016] [error] [client 193.169.252.98] [host andreas.rauhut.eu] (103)Software caused connection abort: Failed to flush CGI output to client
the web log contains lots of information that I am not able to understand completely:
I attach a file with some lines of the log.
my IP : 95.222.27.102
Hope you are able to se something
Both MAUPILLÉ & RAUHUT families are using webtrees V2.1.18
Please Log in or Create an account to join the conversation.
- Andreas
- Offline
- Premium Member
95.222.27.102 wt.rauhut.eu - [31/Dec/2016:16:06:18 +0100] "GET /admin_modules.php HTTP/1.1" 500 25 " wt.rauhut.eu/admin_module_sidebar.php " "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0"
The return code 500 is telling me thats an error. And how can I find more detailed information ?
Both MAUPILLÉ & RAUHUT families are using webtrees V2.1.18
Please Log in or Create an account to join the conversation.
- eh215
- Offline
- Senior Member
There should be an error log as well. If your host company uses CPANEL as the interface, look for an Error Log icon. If you are on a shared host, the log will show a large log file with errors that came from each of the sites hosted on that server, often highlighting those for you in red.
Because that log can be very active if there are many web sites on the same server, you may need to open two browser windows, one for your site and one for the error log.
Trigger the error on your site and then refresh the window with the error log and you should find some messages that will help Greg.
Eric
Please Log in or Create an account to join the conversation.
- Andreas
- Offline
- Premium Member
I switched back to php 7.0 and I'm not able to open the module managing page. That's all. I don't find a way to have more detailed information than the 500 error
95.222.27.102 wt.rauhut.eu - [01/Jan/2017:16:01:02 +0100] "GET /admin_modules.php HTTP/1.1" 500 25 " wt.rauhut.eu/admin_site_config.php?action=site " "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0"
Both MAUPILLÉ & RAUHUT families are using webtrees V2.1.18
Please Log in or Create an account to join the conversation.
- bertkoor
- Offline
- Platinum Member
- Greetings from Utrecht, Holland
Remove their folder(s) then chances are you can get into module administration again.
Try add the custom modules again, one by one. Once you found the offending one: contact the developer you have an issue with php7.
stamboom.BertKoor.nl runs on webtrees v1.7.13
Please Log in or Create an account to join the conversation.