You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was identified over the course of #2095 and #2137.
OctoPrint sorts the sub wizards in the setup wizard by the locale dependent title. Sub wizards marked as mandatory are sorted first, then optional sub wizards follow. This leads to the sub wizard order of
Access Control
Online connectivity check
when english locale is selected. However, in a different locale (e.g. german), ACL setup might get sorted AFTER the mandatory online connectivity check:
Onlineprüfung (Online connectivity check)
Zugangsbeschränkung (Access Control)
That in turn then can't be completed because the API it requires for this denies access as long as ACL setup has not been done yet. The result is that the whole wizard can never be completed.
Solution
It must be ensured that the ACL sub wizard - if required - ALWAYS comes first. Normally we could use the sorting order configuration for that, but in this particular case it is safer to actually hard code this as a special sorting algorithm right into the template processing in the core application, since otherwise a vendor or user might break initial setup simply by configuring a different order.
The text was updated successfully, but these errors were encountered:
Problem
This issue was identified over the course of #2095 and #2137.
OctoPrint sorts the sub wizards in the setup wizard by the locale dependent title. Sub wizards marked as mandatory are sorted first, then optional sub wizards follow. This leads to the sub wizard order of
when english locale is selected. However, in a different locale (e.g. german), ACL setup might get sorted AFTER the mandatory online connectivity check:
That in turn then can't be completed because the API it requires for this denies access as long as ACL setup has not been done yet. The result is that the whole wizard can never be completed.
Solution
It must be ensured that the ACL sub wizard - if required - ALWAYS comes first. Normally we could use the sorting order configuration for that, but in this particular case it is safer to actually hard code this as a special sorting algorithm right into the template processing in the core application, since otherwise a vendor or user might break initial setup simply by configuring a different order.
The text was updated successfully, but these errors were encountered: