Tags get reordered in Admin upon saving?!

Support
1

I have come across a thing that really stumps me. So I have two websites that use tags. On website A, when I post an article with tags, they appear on the article’s page in the order I posted them. Also, when I remove a tag in Admin and add it in a different place of the tags list, then save, they are saved like that and appear on the frontend page in the new sequence. So far so good, this is expected behaviour.

However, when I change the tag order in Admin for a post on website B and click save, the tags will reappear in the new order on the frontend, BUT the tags get reordered in Admin, back to the original order, so on the next save it’s reverted in the frontend as well.

I tried removing them all and saving and then readding the tags in a different sequence, but they still get reordered in the Admin tag field, after they’ve been saved correctly.

It seems to me that the tags’ ordering always follows the same sequence, regardless of which I add or on what article.

The only relevant difference between the two website I can see is that website A uses just the default “tags”, whereas website B uses six different custom types of tags. The problem is the same for all of these. However, I tried adding “tags” to that website, and those also get reordered upon saving.

Is this a bug? Should I put it in the Github issues? Does anybody have any ideas about this?

2

@Netzhexe, In general the same piece of software will always yield the same result…

Unless:

  • the sofware versions differ (Grav, Admin, Form, theme, plugins, custom Twig, etc)
  • configuration differs
  • OS, its type, version and/or config differs
  • input data differs
  • …

You’ve two different sites, which could mean any of the above applies… That makes it hard to pinpoint the issue.

Also comparing Admin with front-end values adds variability. The value saved in the page file would be more interesting to start with.

So, eliminate all variables and try to find a minimal reproducible case. Preferably using a skeleton we can download and test your reproducible script on.

3

That is a good point, though not easily done. I will confer with my client about how they want to handle this, so I may report back or not. Thank you for your input!