OJS 3.2.1.4 Ordering section problem

Software Support
,
1

Hello everyone!

We are using OJS 3.2.1.4. I’ve a problem ordering the sections inside an issue. The same problem described in:

So, I’ve updated the table ‘custom_section_orders’, with the issue and sections IDs, but nothing change. No errors on the log files.

The JSON posted to the server is correct, as I have to put the section_id 81 after the 80:

[
  {
    "categoryId":"61",
    "rowsId":["61","13305"]
  },
  {
    "categoryId":"78",
    "rowsId":["78","13265","13212","13277","13278","13298"]
  },
  {
    "categoryId":"79",
    "rowsId":["79","13302","13316"]
  },
  {
    "categoryId":"80",
    "rowsId":["80","13171"]
  },
  {
    "categoryId":"81",
    "rowsId":["81","13229"]
  },
  {
    "categoryId":"258",
    "rowsId":["258","13216","13274"]
  },
  {
    "categoryId":"82",
    "rowsId":["82","13303","13299"]
  },
  {
    "categoryId":"323",
    "rowsId":["323","13324"]
  },
  {
    "categoryId":"84",
    "rowsId":["84","13322"]
  }
]

And the rows in the ‘custom_section_orders’ table are also correct (as far as I know):

issue_id   section_id  seq
------------------------------------------------
1235       61          1
1235       78          2
1235       79          3
1235       80          4
1235       81          5
1235       258         6
1235       82          7
1235       323         8
1235       84          9

Someone can help me to figure out this bug?
Thank you!

2

Hi @sourcedump,

I believe this issue has already been identified here: New sections added to an Issue can't be custom ordered if the issue has already been custom ordered · Issue #6828 · pkp/pkp-lib · GitHub

There is a PR for it, but I’m not sure it is compatible with 3.2. It’s flagged for the next release of 3.3 (3.3.0-9), but I can talk to our developers about it, and see if it would be prudent for 3.2 - let me get back to you on this.

-Roger
PKP Team

3

Hi @sourcedump,

Heard back from our developers, and there are not any plans to backport this fix to the release that you’re using. You’re welcome to apply the patch to your instance, but there are no guarantees it will work (it was done with the 3.3 code base in mind and will be included as part of the 3.3.0-9 release - probably due out early in next year). I’d suggest ensuring that you have backups before attempting a patch.

-Roger
PKP Team

5

Hi @rcgillis ,
Thanks for the info!