"Reorder categories" button doesn't work in 3.2.0-beta3

Support
1

Hello!

Just installed discourse and imported a bunch of categories and posts from myBB forum. When clicking the Reorder Categories button
image
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:
image

We’re a bit stuck, any help would be greatly appreciated.

2 Likes
2

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:

SCR-20231228-pdkf
SCR-20231228-pdkf1436×66 12.5 KB

5 Likes
3

Hello Mr Taylor,

yes we are running
image

1 Like
4

any non official plugins?

5

No plugins at all

3 Likes
6

From what I see, the fix (Nov 13) was added a few days after 3.2.0-beta4 started (Nov 9). :thinking:

1 Like
7

Rgr. We reverted to 3.1 temporary and things work fine there.

1 Like
8

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.

4 Likes
9

No, we only downgraded the Discourse software, database and everything else remained the same.

10

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.

1 Like
11

Rgr, we updated to tests-passed release path, all issues seem to be resolved.

4 Likes
12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.