Hi
Some of our journals prefer to receive all manuscript via email and not via the submission option in OJS. Is it possible to remove that functions from the settings, so it won’t show up on the UI? See the following page:
They want to keep the access to make a registration as a reader
Best
Niels Erik
For the journals that have requested this, I have just added a modfied submissions.tpl to their child theme folder and removed that section.
But I think disabling the submissions altogether in could be worth a setting in OJS, @asmecher?
Hi all,
I think if you disable author self-registration, users won’t be able to see the option to submit. Some of the default language would need to be changed so as not to suggest that submissions are open, but OTOH I think those are in journal setup.
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher
I do not think this is controlled by the self-registration setting: https://github.com/pkp/pkp-lib/blob/master/templates/frontend/pages/submissions.tpl#L18-L31. Basically users that are not logged in will see the text “{$login} or {$register} to make a submission.” anyway.
It would make sense that if you do not allow submissions through the system, that whole section would be hidden from the submissions page. This is also part of a larger suggestion here: [OJS] Introduce "Publish only" mode to OJS/OMP to simplify workflow · Issue #3639 · pkp/pkp-lib · GitHub
Hi @ajnyga,
Ah, you’re correct, and it wouldn’t make sense to hide/show that text based on the ability to self-register. The issue you filed captures the requirement well.
Regards,
Alec Smecher
Public Knowledge Project Team
I am not sure if the self-register setting should be regarded as a setting that controls submissions. What if a journal wants to allow registrations to reader role but does not want to allow submissions through the system?
Hi @ajnyga,
Yes, that’s what I meant – the self-registration setting is not a good fit for this. Let’s continue on the issue you filed.
Regards,
Alec Smecher
Public Knowledge Project Team
ah sorry, I read “it would make sense” 
See Alec, even potus makes mistakes like this!
…oof…
Regards,
Alec Smecher
Public Knowledge Project Team
Although I’ve disabled author self-registration but enabled reader self-registration there’s still a problem, cause when you login as reader and go to ‘View Profile’ you’ll see the New Submission link in the left menu. Although you only have the reader role, you’re still able to make a new submission. That was not the intention, I guess.
Regards
Niels Erik
I think OJS just does not have a “disable submissions” setting at the moment. It should and I think @asmecher agreed. So it is just a matter of coding it in I guess.
Will this problem soon be solved? It hasn’t been solved in the OJS 3.1.1.4
sry, have not had the time, but this is on my todo list.
Great. Thank you very much.
How is this going???
Hi,
I’m not sure if the problem has been solved in the latest edition, we’re using OJS 3.1.1.4
FYI, a conversation about the same feature has also been started here: Ability to disable submissions in OJS3 · Issue #5702 · pkp/pkp-lib · GitHub
To disable submissions, for each Section check the checkbox “Items can only be submitted by Editors and Section Editors.”
When this is done for all sections, the “Make a new submission” link on the Submissions page will change into “This journal is not accepting submissions at this time” for all roles other than editors.
I hope it’s not a problem that I’m reopening this post after 5 years, but I couldn’t find a more recent topic on this matter. The editorial boards of the journals for which I work as an OJS administrator had a very specific request — namely, to hide the “login or register to make a submission” links/buttons on the “submissions” page, while still keeping registration and login open. Since OJS doesn’t account for such a specific need, I tried a makeshift method — editing the template — and I hope it will be useful to someone and save some time. I located the template responsible for displaying the page: /lib/pkp/templates/frontend/pages/submissions.tpl and commented out (using the {* *} markers) the lines in the following fragment:
<div class="cmp_notification">
{if $sections|@count == 0 || $currentContext->getData('disableSubmissions')}
{translate key="author.submit.notAccepting"}
{else}
{if $isUserLoggedIn}
{* {capture assign="newSubmission"}<a href="{url page="submission"}">{translate key="about.onlineSubmissions.newSubmission"}</a>{/capture}
{capture assign="viewSubmissions"}<a href="{url page="submissions"}">{translate key="about.onlineSubmissions.viewSubmissions"}</a>{/capture}
{translate key="about.onlineSubmissions.submissionActions" newSubmission=$newSubmission viewSubmissions=$viewSubmissions}
*}
{else}
This operation resulted in removing the text but leaving the frame, which is fine for me, but I believe commenting out the entire cmp_notification div will also remove the frame. Of course, this step needs to be repeated after every update, as I believe the code will be overwritten.