Admin Dashboard Becomes Unresponsive After Upgrading to v2.2.4
-
I'm able to load the forum after upgrading to v2.2.4, but when I go to the admin dashboard, none of the buttons/tabs are responsive. The error in the console shows:
GET https://www.domain.com/assets/admin.min.js?v=7gmqq2lle45 Failed to load 'https://www.domain.com/assets/admin.min.js?v=7gmqq2lle45'. A ServiceWorker intercepted the request and encountered an unexpected error. Uncaught ReferenceError: $ is not defined prepareFooter https://www.domain.com/admin:787 EventListener.handleEvent* https://www.domain.com/admin:781 admin:787:4 prepareFooter https://www.domain.com/admin:787 (Async: EventListener.handleEvent) <anonymous> https://www.domain.com/admin:781
For what it's worth we are using Slick as our theme.
-
Can you try
./nodebb stop ./nodebb build ./nodebb start
And pretty me know if you see any errors during that process
-
Can you follow the steps below and tell me what happens next?
-
Reset server which nodebb working on.
-
Deactive theme
-
Active theme
Also please share which plugins you are using on?
-
-
@PitaJ said in Admin Dashboard Becomes Unresponsive After Upgrading to v2.2.4:
Can you try
./nodebb stop ./nodebb build ./nodebb start
And pretty me know if you see any errors during that process
While building, I received these two errors:
ERROR in ./build/public/scripts-client.js 1790:4-1792:6 Module not found: Error: Can't resolve 'slick/chats' in '/Users/name/path/nodebb/build/public' ERROR in ./build/public/scripts-client.js 1800:4-1802:6 Module not found: Error: Can't resolve 'slick/quickreply' in '/Users/name/path/nodebb/build/public'
The first thing I checked was the js files in Public folder. For some reason we don't have the js files for chat and quickreply there so I copied the js files from the slick theme repo to our forums. Ran build, but I received the same errors above.
-
@cagatay said in Admin Dashboard Becomes Unresponsive After Upgrading to v2.2.4:
Can you follow the steps below and tell me what happens next?
-
Reset server which nodebb working on.
-
Deactive theme
-
Active theme
Also please share which plugins you are using on?
I activated the default Slick theme and my admin page is responsive again. I forgot to mentioned in my original post that we are using a custom Slick theme. So I believe the culprit is in our custom theme. I just need to figure out what's causing it.
-
-
@PitaJ quick update: I switched theme as @cagatay suggested above, then switched back to our custom theme and the admin page is responsive again. No console errors. But I still see the errors that I mentioned when I run ./nodebb build in the terminal. Do you know how to resolve it?
ERROR in ./build/public/scripts-client.js 1790:4-1792:6 Module not found: Error: Can't resolve 'slick/chats' in '/Users/name/path/nodebb/build/public' ERROR in ./build/public/scripts-client.js 1800:4-1802:6 Module not found: Error: Can't resolve 'slick/quickreply' in '/Users/name/path/nodebb/build/public'
-
@Teemberland said in Admin Dashboard Becomes Unresponsive After Upgrading to v2.2.4:
@PitaJ quick update: I switched theme as @cagatay suggested above, then switched back to our custom theme and the admin page is responsive again. No console errors. But I still see the errors that I mentioned when I run ./nodebb build in the terminal. Do you know how to resolve it?
ERROR in ./build/public/scripts-client.js 1790:4-1792:6 Module not found: Error: Can't resolve 'slick/chats' in '/Users/name/path/nodebb/build/public' ERROR in ./build/public/scripts-client.js 1800:4-1802:6 Module not found: Error: Can't resolve 'slick/quickreply' in '/Users/name/path/nodebb/build/public'
Nevermind. I was able to fix this by moving the js files from lib to public folder.
-
-
-
@Teemberland compare plugin.json in your custom theme to the original one in the slick plugin.
Likely your theme is not updated for v2 compatibility.
-
@julian said in Admin Dashboard Becomes Unresponsive After Upgrading to v2.2.4:
@Teemberland compare plugin.json in your custom theme to the original one in the slick plugin.
Likely your theme is not updated for v2 compatibility.
Right. That is my guess. I'll report back in a few.