ElementRed/AeroBlack/General
Posted: 8. March 2010 04:18
Your Portal Version: 1.0.5
Your phpBB Type: Standard phpBB3
MODs installed: No
Your knowledge: Basic Knowledge
Boardlink: http://www.clanoneup.com
PHP Version: 3.0.7-PL1
What have you done before the problem was there?
Tried to add AeroBlack to my site, followed all instructions, didn't work.
Tried to add ElementRed to my site, followed all instructions, didn't work.
Tried refreshing templates, themes, imagesets.
Purge forum cache and my browsers cache.
What have you already tryed to solve the problem?
Triple checked my work.
Description and Message
I recently updated my board to 3.0.7-PL1 and now my portal doesn't work, even on the default skins.
My index page works for the forum, even when i preview an installed style. When I redirect my browser to www.clanoneup.com/portal.php
I get this:
I haven't deleted anything or edited anything other than what is said in the instructions for style installs.
Any clue what happened? Or is this just an incompatibility problem with 3.0.7-PL1 that needs to be addressed.[/i]
Your phpBB Type: Standard phpBB3
MODs installed: No
Your knowledge: Basic Knowledge
Boardlink: http://www.clanoneup.com
PHP Version: 3.0.7-PL1
What have you done before the problem was there?
Tried to add AeroBlack to my site, followed all instructions, didn't work.
Tried to add ElementRed to my site, followed all instructions, didn't work.
Tried refreshing templates, themes, imagesets.
Purge forum cache and my browsers cache.
What have you already tryed to solve the problem?
Triple checked my work.
Description and Message
I recently updated my board to 3.0.7-PL1 and now my portal doesn't work, even on the default skins.
My index page works for the forum, even when i preview an installed style. When I redirect my browser to www.clanoneup.com/portal.php
I get this:
Code: Select all
SQL ERROR [ mysql4 ]
Table 'clanoneu_phpb1.PORTAL_CONFIG_TABLE' doesn't exist [1146]
An sql error occurred while fetching this page. Please contact an administrator if this problem persists.
Any clue what happened? Or is this just an incompatibility problem with 3.0.7-PL1 that needs to be addressed.[/i]