We still have to find a good way to integrate the new plugin, but… You can take the .tar.gz from here: Release ojs-3_0_1-0 · pkp/quickSubmit · GitHub. You will have to remove the current quickSubmit folder in your plugins/importexport/ folder, to extract the package there and rename the new folder to “quickSubmit” instead of (quickSubmit-ojs-3_0_1-0). I checked it right now with the current ojs-stable-3_0_1 branch and it worked for me. How did you try to do it i.e. does this way work for you?
Thanks for your guideline. I follow your guideline to add quickSubmit plugins. I add it to this path (public_html/plugins/importexport/quickSubmit) i also see the quickSubmit plugin in my OJS installation. But when i click quickSubmit plugin from tools menu i get HTTP ERROR 500 and …/management/importexport/plugin/QuickSubmitPlugin this path in url bar.
Hmmm… I tried it with the current ojs-stable-3_0_1 branch and had no problems… I will take a look with the release package – lots of issues were solved/changed since than… Will let you know then… THANKS!!!
Yes, it seems the function changed in the SectionDAO with this commit after the release and the plugin is developed on top of that recent changes: pkp/pkp-lib#2049 Respect section editor-only flag on submission · pkp/ojs@9222f35 · GitHub
I’ll see if we will maybe make another plugin package, to fit to the current OJS 3.0.1 release. Till then you could change the getTitles into getSectionTitles in plugins/importexport/quickSubmit/QuickSubmitForm.inc.php (two times) and I will let you know if there is a new plugin package soon…
Hi @bozana
Thanks for your information.
I successfully use the quicksubmit plugin to publish the old issues in 2015. The problem is the old issue replaced the newest issue as the current issue. The current issue in my journal is Vol 8 No 2 (2015): Nopember. How could I solve this? If I am not mistaken, in Ojs 2.4.xx we can manage the current issue. http://jurnalbeta.ac.id/index.php/betaJTM
Hi all,
To turn the newest issue as the current issue, I unpublished the issue first and published it again. It brings back the current issue. By re-publishing the issue again, the published date changes. I change the date to the original date when I published it. is it the only procedure to do this?
I will be probably be in the Plugin Gallery in the next OJS 3.0.2 release. Now, you would have to get and unpack the package manually/alone, but I would say it is safe to use it already i.e. with the OJS 3.0.1 version…