Unexpected behaviour: things don't work as anticipated when I assign a new version of the forthcoming article to a new issue and publish it. Is this a problem with the plugin, or with my instance?
Details:
1 - Publish new article to Forthcoming: everything behaves as it should
2 - Create a new version of the article and schedule for a future issue
- In the article's Publication>Issues tab, the version appears to be scheduled properly
- In Future Issues, the article isn't reflected in the item count for the issue BUT it does appear in the Table of Contents. However, it also continues to appear in the Table of Contents for the Forthcoming issue.
3 - Publish the issue
- In the article's Publication>Issue tab, it shows as "Scheduled for publication in [new issue]" but not as Published.
- In the Back Issues list, it continues to appear in the table of contents for both the Forthcoming issue and the new issue. It still doesn't appear in the item count for the new issue.
- On the front end, it appears in the table of contents for the Forthcoming issue and for the new issue (the article is entitled "PDF validity check"). The article link from both issues points to version 1 of the article; version 2 does not appear on the front end.
4 - Workaround: I can resolve the problems described in step 3 after publishing by going to Publication>Issue tab of the new version, unscheduling the article, and rescheduling it to the same, new issue.
- In the Publication>Issue tab, it now appears as Published
- In Back Issues, the first version disappears from the Forthcoming issue; both issue's article counts new display the correct information.
- On the front end, the article disappears from the Forthcoming issue; the table of the contents for the new issue now correctly links to the new version.
Context/setup: I'm running OJS 3.3.0.19 and each of my journals runs on a separate instance of OJS. I have been testing the plugin in our OJS sandbox, which has been poked and prodded a lot over the years and may behave idiosyncratically. In case it has implications for chron jobs: during testing I'm performing the initial publication to Forthcoming and the reassignment to and publication of a new issue on the same day. I'm the administrator but I don't have database access - our library IT support does that.
Unexpected behaviour: things don't work as anticipated when I assign a new version of the forthcoming article to a new issue and publish it. Is this a problem with the plugin, or with my instance?
Details:
1 - Publish new article to Forthcoming: everything behaves as it should
2 - Create a new version of the article and schedule for a future issue
3 - Publish the issue
4 - Workaround: I can resolve the problems described in step 3 after publishing by going to Publication>Issue tab of the new version, unscheduling the article, and rescheduling it to the same, new issue.
Context/setup: I'm running OJS 3.3.0.19 and each of my journals runs on a separate instance of OJS. I have been testing the plugin in our OJS sandbox, which has been poked and prodded a lot over the years and may behave idiosyncratically. In case it has implications for chron jobs: during testing I'm performing the initial publication to Forthcoming and the reassignment to and publication of a new issue on the same day. I'm the administrator but I don't have database access - our library IT support does that.