OJS 3.0.2 - Front-end not working for non-logged-in users

Software Support
1

Hi there,

I am currently in the process of installing and configuring OJS and it’s looking like a fantastic piece of software, so first off - thankyou for providing it!

Now, onto the problem …

We have created a Journal but now when people visit it (without registering or being logged in) they receive a 404 page. However if a logged in user views the same page they can see the journal without issue.

The journal is at

https://www.orbit-rri.org/ojs/index.php/orbit/

The following is from our error_log which is growing at a rapid rate … is this usual?

[09-Aug-2017 10:01:02 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getSeq() should be compatible with BlockPlugin::getSeq($contextId = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:01:02 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getBlockContext() should be compatible with BlockPlugin::getBlockContext($contextId = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:01:02 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getEnabled() should be compatible with BlockPlugin::getEnabled($contextId = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:01:02 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getContents() should be compatible with BlockPlugin::getContents($templateMgr, $request = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::checkFrequency() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/plugins/generic/acron/PKPAcronPlugin.inc.php on line 315
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::_isInRange() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/scheduledTask/ScheduledTaskHelper.inc.php on line 114
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::checkFrequency() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/plugins/generic/acron/PKPAcronPlugin.inc.php on line 315
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::_isInRange() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/scheduledTask/ScheduledTaskHelper.inc.php on line 114
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::checkFrequency() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/plugins/generic/acron/PKPAcronPlugin.inc.php on line 315
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::_isInRange() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/scheduledTask/ScheduledTaskHelper.inc.php on line 114
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::checkFrequency() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/plugins/generic/acron/PKPAcronPlugin.inc.php on line 315
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::_isInRange() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/scheduledTask/ScheduledTaskHelper.inc.php on line 114
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::checkFrequency() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/plugins/generic/acron/PKPAcronPlugin.inc.php on line 315
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method ScheduledTaskHelper::_isInRange() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/scheduledTask/ScheduledTaskHelper.inc.php on line 114
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method Request::getContext() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/plugins/ThemePlugin.inc.php on line 409
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method PKPRequest::_checkThis() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/classes/core/Request.inc.php on line 68
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method Request::getContext() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/plugins/ThemePlugin.inc.php on line 409
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method PKPRequest::_checkThis() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/classes/core/Request.inc.php on line 68
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getSeq() should be compatible with BlockPlugin::getSeq($contextId = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getBlockContext() should be compatible with BlockPlugin::getBlockContext($contextId = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getEnabled() should be compatible with BlockPlugin::getEnabled($contextId = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Declaration of CustomBlockPlugin::getContents() should be compatible with BlockPlugin::getContents($templateMgr, $request = NULL) in /home/respons3/public_html/ojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 130
[09-Aug-2017 10:02:55 Europe/London] PHP Strict Standards:  Non-static method PKPRequest::_checkThis() should not be called statically, assuming $this from incompatible context in /home/respons3/public_html/ojs/lib/pkp/classes/core/Dispatcher.inc.php on line 245
[09-Aug-2017 10:02:55 Europe/London] ojs2: 404 Not Found
2

You should change the visibility of the journal. It is probably hidden at the moment.

Administration => Hosted journals => click the blue triangle in the front of you journal => edit => Enable this journal to appear publicly on the site

2 Likes
3

Man alive! So simple …

Thank you!

2 Likes
4

Hi @keeno79,

As for those warnings – they’re cosmetic, and due to the stricter standards that recent releases of PHP hold the code to. Many of these will be resolved with the next release of OJS, and in the meantime, you can ignore them.

Regards,
Alec Smecher
Public Knowledge Project Team

5

The problem still persists with weird system behaviour when public display is set to off. Our problem is this: We are running a multi-journal environment (OJS 3.1.0.1, the release notes for 3.1.1 do not mention any change) where we want to hide journals that have not finished their set up. Once we disable visibility, the journal link no longer works (OJS returns 404), therefore journal managers cannot log in using that link. This also happens when users log in via the portal page, go to the journal, and log out again. This is not expected behaviour for us, the direct link should work regardless of the visibility setting. Can we expect a fix for this anytime soon?

6

Hi @ojs_univie,

I’ve filed this issue at Login page for disabled contexts not available · Issue #3834 · pkp/pkp-lib · GitHub and proposed a fix over there. If you’re able to test the proposed change, your feedback would be welcome.

Regards,
Alec Smecher
Public Knowledge Project Team

7

We would prefer everything working normally (with no need for logging in) with the only consequence of this setting being that the journal is invisible on the portal page. IIRC this used to be the OJS2 behaviour. Anything is better than a 404 screen though.