The “Reorder categories” button is not working in Discourse version 3.2.0-beta3, throwing a console error Darojax. david asked for the precise version, which was provided as 3.2.0-beta3 Darojax. sam inquired about non-official plugins, but none were present Darojax. Arkshine noted that the fix for this issue was added after the 3.2.0-beta4 release. As a temporary solution, Darojax reverted to version 3.1, but david warned about potential issues due to the database schema mismatch. RGJ advised against downgrading Discourse. Darojax eventually updated to the “tests-passed” release path, resolving all issues.
nothing happens and the console throws the following error:
rsvp.js:23 Uncaught TypeError: Cannot read properties of undefined (reading 'show')
at m.reorderCategories (navigation.js:59:16)
at e.selectCategoryAdminDropdownAction (d-navigation.js:175:16)
at $._join (index.ts:646:21)
at $.join (index.ts:362:17)
at p (index.js:156:1)
at index.js:707:1
at e.flaggedInstrument (index.js:126:1)
at index.js:706:1
at Object.onChange (index.js:665:1)
at e._onChange (categories-admin-dropdown.js:37:18)
at e._boundaryActionHandler (select-kit.js:410:38)
at select-kit.js:330:12
at rsvp.js:459:1
at new R (rsvp.js:915:1)
at e._onChangeWrapper (select-kit.js:312:12)
at $._join (index.ts:646:21)
at $.join (index.ts:362:17)
at p (index.js:156:1)
at s.change (index.js:257:1)
at e.select (select-kit.js:597:22)
at $._run (index.ts:665:23)
at $._join (index.ts:640:19)
at $.join (index.ts:362:17)
at p (index.js:156:1)
at s.select (index.js:257:1)
at e.click (select-kit-row.js:91:20)
at e.trigger (core_view.js:63:1)
at e.r [as trigger] (index.js:383:1)
at e.trigger (ember-events.js:138:30)
at e.r [as trigger] (index.js:383:1)
at HTMLLIElement.o (ember-events.js:203:39)
This seems like a duplicate of this older issue?
But we are running the latest version:
We’re a bit stuck, any help would be greatly appreciated.
Hey @Darojax - please could you let us know the precise version of Discourse you’re running. If you open your browser developer console (right click the page → inspect element → console), you should see something like this:
Yup, exactly what @Arkshine said. We’ll be releasing beta4 in the next week or two. So if you want to stick with the ‘beta’ release path you’ll need to wait until that happens. Alternatively, you could switch to the default ‘tests-passed’ release path, which is what the vast majority of people use (including our official paid hosting).
Did you revert the database from a backup? If not, and you’re running 3.1 against a 3.2.0.beta3 database schema, you may run into some other strange failures.
You cannot downgrade Discourse, which is what you effectively did.
Weird problems will haunt you for years if you do that.
You should go back to the latest version ASAP.
