502-fout bij opnieuw ordenen van categorieën


  • this issue has existed for months
  • today the forum has about 405 categories
1 like

Ik vermoed dat uw server gewoon te traag is om de taak te volbrengen. Honderden categorieën worden niet echt aanbevolen.

De manier waarop ik honderden categorieën eerder heb gesorteerd, was in rails.

1 like

Ah – this problem was actually why I chose the IONOS VPS L. Previously I found better performance with the IONOS Data Center Designer, where I was also using a VPS. I’ve never experienced the Dedicated Core offering, which could potentially null this issue, but I believe the Designer VPS had faster NVMe and maybe higher per-core turbo.

The UI loading of the composer’s category selector is slow, but that encourages people to browse into the desired category first, IMHO.

Nice - I think we’re into the command line vs. UI discussion again :rofl:

1 like

Here’s something I recommended to someone else (that I still haven’t tested).

1 like

You’re doing some crazy stuff with Discourse, Ethan! :rofl:

Were you able to resolve your issue?

Haha thanks Tobias! :grinning_face_with_smiling_eyes:

It only happened that one time — I haven’t run any Rails commands or anything like that, just through the UI. The same operation worked after retrying, so it looked like a temporary 502 rather than a lasting issue.

Haven’t needed to re-order categories since, so it’s not bothering me now. :slightly_smiling_face:

1 like