Hmmm… The upgrade then seems to be fine/successful…
The site index page maybe looks different because there is still a CSS used from OJS 2.4.x i.e. uploaded in OJS 2.4.x?
And regarding the second error: when you open the broser developer tools do you see any errors?
Strange situation… 
good hint, I disabled the old stylesheets and it looks a bit better 
but I still get this error message and I can’t configure anything, see:
this is really exhausing… and we didn’t have any problems with the other migrations.
Is there a possiblity to migrate without using the mysql-dump? I thought, whether it would be possible to export/import the files into a new ojs3-system. As we don’t have many registered users in the old system I could register these people manually.
Could this work?
Good morning Bozana,
this morning I installed OJS3 completly from scratch, which worked fine. I could open the journal gui via Journal of Global Theatre History as defined in the config.inc.
But when I tried to login as admin I get the same problems as yesterday: I am again in a general OJS installation, I can’t see my journal and the URL changes to https://gthj-ojs3test.ub.uni-muenchen.de/**index.php/index/**user/profile
Do you have any idea, what could be the reason for this strange behavior? The apache configuration is completly the same as the other journals, which work without problems
Thanks, Anna
The apache error log tells me this:
[Fri Feb 23 09:32:51.809828 2018] [:error] [pid 31003] [client 10.153.124.104:50364] PHP Warning: Declaration of CategoryGridHandler::doSpecificFetchGridActions($args, $request, &$templateMgr) should be compatible with GridHandler::doSpecificFetchGridActions($args, $request, $templateMgr) in /opt/ojs-gthj/lib/pkp/classes/controllers/grid/CategoryGridHandler.inc.php on line 0, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/admin/systemInfo
[Fri Feb 23 09:32:51.810799 2018] [:error] [pid 31003] [client 10.153.124.104:50364] PHP Warning: Declaration of SystemInfoGridCategoryRow::initialize($request) should be compatible with GridRow::initialize($request, $template = NULL) in /opt/ojs-gthj/lib/pkp/controllers/grid/admin/systemInfo/SystemInfoGridCategoryRow.inc.php on line 0, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/admin/systemInfo
[Fri Feb 23 09:32:51.810876 2018] [:error] [pid 31003] [client 10.153.124.104:50364] PHP Warning: Declaration of SystemInfoGridHandler::initialize($request) should be compatible with CategoryGridHandler::initialize($request, $args = NULL) in /opt/ojs-gthj/lib/pkp/controllers/grid/admin/systemInfo/SystemInfoGridHandler.inc.php on line 19, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/admin/systemInfo
[Fri Feb 23 09:32:51.810927 2018] [:error] [pid 31003] [client 10.153.124.104:50364] PHP Warning: Declaration of SystemInfoGridHandler::loadCategoryData($request, $configSection) should be compatible with CategoryGridHandler::loadCategoryData($request, &$categoryDataElement, $filter = NULL) in /opt/ojs-gthj/lib/pkp/controllers/grid/admin/systemInfo/SystemInfoGridHandler.inc.php on line 19, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/admin/systemInfo
[Fri Feb 23 09:33:01.525782 2018] [:error] [pid 31044] [client 10.153.124.104:50366] PHP Warning: Declaration of ContextGridHandler::loadData($request) should be compatible with GridHandler::loadData($request, $filter) in /opt/ojs-gthj/lib/pkp/controllers/grid/admin/context/ContextGridHandler.inc.php on line 0, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/admin/contexts
[Fri Feb 23 09:33:01.526546 2018] [:error] [pid 31044] [client 10.153.124.104:50366] PHP Warning: Declaration of ContextSiteSettingsForm::fetch($request) should be compatible with Form::fetch($request, $template = NULL, $display = false) in /opt/ojs-gthj/lib/pkp/controllers/grid/admin/context/form/ContextSiteSettingsForm.inc.php on line 19, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/admin/contexts
[Fri Feb 23 09:35:56.039688 2018] [:error] [pid 30868] [client 10.153.124.104:50390] PHP Warning: Declaration of BaseProfileForm::execute($request, $user) should be compatible with Form::execute() in /opt/ojs-gthj/lib/pkp/classes/user/form/BaseProfileForm.inc.php on line 18, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/user/profile
[Fri Feb 23 09:35:56.039753 2018] [:error] [pid 30868] [client 10.153.124.104:50390] PHP Warning: Declaration of IdentityForm::execute($request) should be compatible with BaseProfileForm::execute($request, $user) in /opt/ojs-gthj/lib/pkp/classes/user/form/IdentityForm.inc.php on line 18, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/user/profile
[Fri Feb 23 09:35:56.039780 2018] [:error] [pid 30868] [client 10.153.124.104:50390] PHP Warning: Declaration of IdentityForm::fetch($request) should be compatible with Form::fetch($request, $template = NULL, $display = false) in /opt/ojs-gthj/lib/pkp/classes/user/form/IdentityForm.inc.php on line 18, referer: https://gthj-ojs3test.ub.uni-muenchen.de/index.php/index/user/profile
[Fri Feb 23 09:37:11.932135 2018] [:error] [pid 30869] [client 142.58.129.152:59906] ojs2: 404 Not Found
1 Like
Hi @akku
Phew…
Regarding the existing installation migration without CSS: when you log-in, you only see empty pages e.g. that “Aussehen” tab, right? When you open the browser developer console and network tag (e.g. in Firefox: right click > Inspect Element > Console and Network, then call the page), do you see any errors there after you open that page?
Regarding the new installation: I did not understand what was here the problem – the same as for the other one – blank page and 404 Not Found error message? Also here, when you open the browser developer console and network tab?
Else, the export → import migration is not easy because the XML format changed. Also this way a lot of other things could not be migrated. Thus, better to migrate it correctly.
What plugins does this problematic journal use?
Best,
Bozana
problem solved 
I deleted again everything from the server and did a new upgrade: again only the “404”-error page. But I managed to get into the administration of the journal and found out that the decision “wollen Sie dass dieses Journal öffentlich zu sehen ist?” was disabled. After enabling it, I could see the journal.
Weekend can start. Thank you very much for your support,
Anna
Great! 
