Bug order back issues? (OJS)

InfoDocu · November 16, 2021, 12:41pm

I use 3.1.2.4 OJS. I’m having trouble saving a back issues order. In particular, I click “done” but it doesn’t save the order. “Done” does nothing. It has worked for months and suddenly it has stopped working.

Are there any bug reported about it? What can happen?

Thank you.

jnugent · November 16, 2021, 1:41pm

Hi @InfoDocu

That’s a really old version of OJS 3, so my first suggestion is an upgrade to see if that resolves the problem. There was a bug related to custom ordering in an issue’s table of contents, filed here:

github.com/pkp/pkp-lib

New sections added to an Issue can't be custom ordered if the issue has already been custom ordered

opened 02:55PM - 05 Mar 21 UTC

closed 12:00PM - 26 Jun 21 UTC

jnugent

Hosting Bug

**Describe the bug** If an issue is created, and articles in various sections… are added to this issue, and then the issue is ordered in a custom way so that sections are moved around, new sections added later on can't be ordered. It's possible to move them around in the TOC grid, but when you click save they will revert partially. The grid will remember the order for the first time you customize ordering, but not for anything you add to that issue later on. I believe this is because `setDefaultCustomSectionOrders` is only called initially, in `setDataElementSequence` in `TocGridHandler` if the `sectionDao` does not detect an existing custom order. There's no other entry point to insert the records needed for ordering in custom_section_orders after that first go around, and future calls to `resequenceCustomSectionOrders` will not find the newly added sections to the issue's table of contents. **To Reproduce** Steps to reproduce the behavior: 1. Create a new empty issue. 2. Ensure that you have at least three journal sections created. 3. Publish an article in one of those sections and add it to the issue. 4. Publish a second article in a different section and add it to the same issue. 5. Edit the issue and re-order the two sections. This will save correctly. 6. Publish a third article in a new section, and add it to the issue. 7. attempt to reorder the issue's table of contents, by moving this new section to the top. 8. It should not save and will revert when ordering is finished. **What application are you using?** Seen in 3.3.0, 3.2.1-3

But that sounds different.

Best,
Jason

InfoDocu · November 16, 2021, 4:29pm

Hi @jnugent

Thanks for your quick response.

I will wait a few days before updating. It is a delicate process and I would prefer not to do it.

The point is that it worked yesterday and not today. I want to locate the origin. Is there a file that records these errors? I don’t think so because OJS doesn’t actually show any error messages, it just doesn’t work.

In over 8 years using OJS I have never seen anything like it.

jnugent · November 16, 2021, 4:43pm

Hi @InfoDocu

This sounds like this bug here:

Which was ultimately fixed in 3.2.1, perhaps 3.2.1-2. The bug I linked to previously would not save a new order if you had already ordered it but that bug was for tables of content.

Cheers
Jason

InfoDocu · November 17, 2021, 8:34am

Hi @jnugent

Thank you for showing me similar cases.

For now I have not been able to solve it but I have discovered the specific situation in which it happens.

This is when I publish a new issue and it is moved from “future issues” to “back issues”. If I don’t add a new issues in “back issues” the “back issues” list I can order it and save it.

On the other hand, is there no chance of knowing that it is failing? It’s weird that I’ve been working for a year and suddenly not anymore.

I will be writing in this post if I have news in case someone is helpful. I hope I don’t have to update but it is very likely

Regards.

InfoDocu · November 22, 2021, 12:49pm

Hello again,

I have continued researching this bug. I have located in the file “apache.error.log” the line where I think the error appears. Would it provide any clues?

On the other hand, is it possible to solve it by changing any line of a file? Hi, @asmecher I saw that you provided this solution for a similar case.

Do you know what could be done in this case? Or upgrade to 3.3.0-8?

Thank you very much for your time.

InfoDocu · February 8, 2022, 2:44pm

Hello everybody

I found the solution to this situation and it might be the same for tables of contents.

It was a firewall that was blocking the request to save changes because it was detected as suspicious.

I hope it helps other people and saves them time.