[OJS 3.1.1] Create Journal loads indefinitely, journal db exists, but all Javascript missing

Hello, I am using Windows 10 and XAMPP to install OJS.
I am using PHP 7.2.3, with pdo_mysql and pdo_sqlite enabled.
image
I installed OJS by first adding “authorised” user via the phpMyAdmin page.
Then when I clicked “Create Journal”, the Console sends this warning
image
The others were hidden but the most obvious one is
jquery.js:9627 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Which then points to here
image
xhr.open( options.type, options.url, options.async, options.username, options.password );
After I fill in the fields and went on clicking “SAVE”, it loads indefinitely and gives the following error message
image
jquery.js:9666 POST http://localhost/ojs/index.php/index/$$$call$$$/grid/admin/journal/journal-grid/update-context 500 (Internal Server Error)
Which points to here
image
xhr.send( ( options.hasContent && options.data ) || null );
Then I clicked on “CANCEL” and refreshed the page
The journal is created, but…
image
It doesn’t have any JS in it, only the html.
image
But the database exists
image

I apologise that English is not my mother tongue, and I don’t have any educational background nor professional experience with IT and Web programming before. But I have followed the required steps which brings me here. Any help will much be appreciated.

layoland

Updated:
The PHP error log says something like this:
image
[15-Apr-2018 07:56:49 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:56:50 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:56:50 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:56:51 Europe/Berlin] PHP Warning: Declaration of ContextGridHandler::loadData($request) should be compatible with GridHandler::loadData($request, $filter) in C:\xampp\htdocs\ojs\lib\pkp\controllers\grid\admin\context\ContextGridHandler.inc.php on line 214
[15-Apr-2018 07:56:51 Europe/Berlin] PHP Warning: Declaration of ContextSiteSettingsForm::fetch($request) should be compatible with Form::fetch($request, $template = NULL, $display = false) in C:\xampp\htdocs\ojs\lib\pkp\controllers\grid\admin\context\form\ContextSiteSettingsForm.inc.php on line 19
[15-Apr-2018 07:56:51 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:56:51 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:57:16 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:57:16 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 07:57:19 Europe/Berlin] PHP Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\ojs\lib\pkp\classes\template\PKPTemplateManager.inc.php on line 1578
[15-Apr-2018 07:57:20 Europe/Berlin] PHP Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\ojs\lib\pkp\classes\template\PKPTemplateManager.inc.php on line 1578

Hi @layoland,

There’s probably something relevant further back in your PHP log; look for something containing the word “error”.

Regards,
Alec Smecher
Public Knowledge Project Team

From top to the bottom there isn’t any “error” words in the php error log.
I tried creating a new journal and this is all I got
[15-Apr-2018 09:05:26 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 09:05:29 Europe/Berlin] PHP Warning: Declaration of ContextGridHandler::loadData($request) should be compatible with GridHandler::loadData($request, $filter) in C:\xampp\htdocs\ojs\lib\pkp\controllers\grid\admin\context\ContextGridHandler.inc.php on line 214
[15-Apr-2018 09:05:30 Europe/Berlin] PHP Warning: Declaration of ContextSiteSettingsForm::fetch($request) should be compatible with Form::fetch($request, $template = NULL, $display = false) in C:\xampp\htdocs\ojs\lib\pkp\controllers\grid\admin\context\form\ContextSiteSettingsForm.inc.php on line 19
[15-Apr-2018 09:05:33 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 09:05:41 Europe/Berlin] PHP Warning: Declaration of PKPUsageEventPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in C:\xampp\htdocs\ojs\lib\pkp\plugins\generic\usageEvent\PKPUsageEventPlugin.inc.php on line 386
[15-Apr-2018 09:05:41 Europe/Berlin] PHP Warning: Declaration of ContextGridHandler::loadData($request) should be compatible with GridHandler::loadData($request, $filter) in C:\xampp\htdocs\ojs\lib\pkp\controllers\grid\admin\context\ContextGridHandler.inc.php on line 214
[15-Apr-2018 09:05:42 Europe/Berlin] PHP Warning: Declaration of ContextSiteSettingsForm::fetch($request) should be compatible with Form::fetch($request, $template = NULL, $display = false) in C:\xampp\htdocs\ojs\lib\pkp\controllers\grid\admin\context\form\ContextSiteSettingsForm.inc.php on line 19

Are you using MariaDB instead of mysql?

This could be the problem?

Yes most likely.
Because I’m using XAMPP as the web server package.
Then, would switching to other program like WAMP help?

Latest XAMPP ships with MariaDB.

Wamp has both Mysql and MariaDB.

Hi all,

MariaDB and MySQL should both work fine.

I suspect you’ve hit a timeout in running the install process. Check to see what your XAMPP configuration’s request timeout is; it should be longer than 30 seconds, which IIRC is the default, at least for the sake of the install process.

Regards,
Alec Smecher
Public Knowledge Project Team

1 Like

i miss the trouble like you, and a don’t know how to fix it. i lose 3 weeks to find but nothing :((. Did you fix it? Can you help me, please!

Hi @Oanh_Hoang,
You need to see your php error_log for any “error”. Then one can know where and what exactly is the problem.

Do you have access to php error_log?

Screenshot%20(43)
hi @anupent I can’t open php error_log on xampp.Can you help me, please!

it’s me, after I create logs in php, it’s show up the php error_log
Screenshot%20(48)

and this is line 1578 in php error_log
Screenshot%20(47)
thank you so much!

They are cosmetic and are helpful for OJS developer team. Not for users like us.

See for something that says “error” in php error_log

I also encounter this error, I fixed it when i change the maximum execution limit and max post limit in php.ini - i am also using xampp php5.6 and go to config.ini.php file in ojs find this CDN = OFF. Hope it help someone too. Delete your first created journal that encounter error and create a new one. By the way I create the second Journal first before i remove the first one that enconter the error.