Your Portal Version: 1.0.6
Your phpBB Type: Standard phpBB3
MODs installed: No
Your knowledge: Advanced Knowledge
PHP Version: 5
MySQL Version: 4
What have you done before the problem was there?
Upgraded from phpbb 3.0.8 to 3.0.10.
What have you already tryed to solve the problem?
Reinstalling the mod, both in file edits and by uninstalling and reinstalling on the database.
Description and Message
I have recently updated this forum from 3.0.8 to 3.0.10 with fresh phpbb files (without mods). Then I uploaded the root files and the file edits for board3 1.0.6, and I refreshed my style and emptied the buffer. Everything seemed fine except /portal.php shows a white page. I have tried reinstalling the mod, but I still get this white page. I hope anybody can help me out as to how I can fix this! Thanks!
Portal 1.0.6 on PhpBB 3.0.10 gives a white page
Forum rules
Before creating a new support thread, please take a look in the board3 Portal FAQ and use the search!
Many questions have already been answered.
Before creating a new support thread, please take a look in the board3 Portal FAQ and use the search!
Many questions have already been answered.
-
Topic author - Active Member
- Posts: 10
- Joined: 30. March 2009 19:17
- phpBB.com User: AylaAsperger
- Location: Netherlands
-
- Dev
- Posts: 2504
- Joined: 17. July 2008 21:08
- phpBB.de User: marc1706
- phpBB.com User: Marc
- Location: Clausthal-Zellerfeld / München
Re: Portal 1.0.6 on PhpBB 3.0.10 gives a white page
Try to re-upload all of Board3 Portal's files again.
-
Topic author - Active Member
- Posts: 10
- Joined: 30. March 2009 19:17
- phpBB.com User: AylaAsperger
- Location: Netherlands
Re: Portal 1.0.6 on PhpBB 3.0.10 gives a white page
I had done that two times already without succes. Also tried to replace the original files one by one to find out which one gave a problem, but that didn't do much either. I did find the problem though, my provider uses php4 standard, and to use the forum with php5 I have to add a handler to .htacces. While updating to 3.0.10 I completely forgot to add that handler and once added the problem was fixed. Thank you for your support!