We Lost Gorgeous George (unreachable category)

Ondersteuning
1

I am puzzled by this bug that hit some time ago. I gave it some time to disappear, and this morning I tried changing the affected categories to see whether it would disappear, but it’s still there, forbidding access to a category that has been there for years.

Symptoms

I have a subcategory with (full) slug asbl:editions. I have another subcategory incoming:ps-editions-lesoiseaux-io. The latter is more recent.

Whenever I tried to move a topic to the former category, or create a new topic there from the home page, etc., when I type editions, I only get the latter in the list, and not the former.

There’s no log, no console error: it’s just not there.

This is very annoying because it’s a very important category and many times I need to move relevant topics there.

Troubleshooting

I would like some guidance to understand how to track down this bug, because there’s no obvious way to do so. This is the only affected category.

I tried:

  • removing the slug and saving :slightly_frowning_face:
  • removing the slug and saving in the other category :slightly_frowning_face:
  • renaming the category to WTF: it appeared again in the dropdowns :slightly_smiling_face:
  • renaming the category back to its original name (Éditions): it disappeared again… :slightly_frowning_face:

I wonder if there is a reserved word issue, or some kind of confusion across category slugs, tags, groups… I have no duplicate name but variants: ps-editions, editions-ps, etc. that use the single word that is the missing category slug: editions. Maybe this is a lead?

Thank you for your helpful attention.

5 likes
3

Does it work if you name your category Editions instead of Éditions? :thinking:

We might be missing a call or two to unaccent on the server side, as I think LIKE and ILIKE don’t work well with diacritics.

SELECT 'Éditions' ILIKE '%editions%'
 ?column?
----------
 f
(1 row)

and when using unaccent

SELECT unaccent('Éditions') ILIKE unaccent('%editions%')
 ?column?
----------
 t
(1 row)
2 likes
4

Bien joué @zogstrip, this is thus a bug in supporting accents. I guess this must be common in non-English languages then.

Happy Discourse anniversary BTW :slight_smile:

5

Thanks :sweat_smile:

I’ve already made a PR for the fix :wink:

2 likes