-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin puts submission files for one submission in multiple folders #3
Comments
@amandastevens, this will depend on a third-party library accepting a pull request (https://github.com/bsobbe/iThenticate/pull/4/files) before I can officially add it. Once that's done I can merge this and prepare a release. In the meantime you can apply cd4096d and https://github.com/bsobbe/iThenticate/pull/4/files manually if it's a rush to support this for someone. |
Thanks, @asmecher. We applied the patch, but when the client re-enabled the Ithenticate plugin it created problems with the submission process. No submissions could be completed, as they were getting stuck on the confirmation step. When the plugin was disabled again, authors were able to submit. |
@amandastevens, did you apply both patches? There's one to the plugin, and one to the library it depends on. |
Oops! We only applied one patch. We've applied the 2nd one now so it should work. Sorry about that! |
Hi, |
The downstream contribution was merged, so closing here. @drugurkocak, you're requesting something different -- see e.g. #12. |
On a Publishing Services client's OJS 3.1.1-4 site the Ithenticate plugin is sending all submission files (including cover letters, title pages, and figures) to Ithenticate, and instead of the files being added to one folder per submission they are being added to separate folders. As a result, there are multiple folders per submission and the client is being charged for each file instead of each submission.
The client contacted Turnitin and they said, "We will process any files which are sent to us but we cannot make OJS send those files so the fault has to be within OJS."
The text was updated successfully, but these errors were encountered: