Console error after upgrade to 2.1.0

phenomlab

@baris said in Console error after upgrade to 2.1.0:

When you run in dev mode click the stack trace and it should open up admin.min.js and hopefully show the related code.

@baris I paused the debugger on error as nothing was being shown in the console. I now see this (there is no stacktrace in the console either)

Which after resuming the debugger and stepping through multiple errors of the above, the console displays this

admin.min.js?v=gqomh6ivrjk:2 
        
       Uncaught TypeError: Cannot read properties of undefined (reading 'jQuery360035230057915444891')
    at Q.cache (admin.min.js?v=gqomh6ivrjk:2:1102691)
    at Q.get (admin.min.js?v=gqomh6ivrjk:2:1102981)
    at Object.add (admin.min.js?v=gqomh6ivrjk:2:1110624)
    at admin.min.js?v=gqomh6ivrjk:2:1109958
    at Function.each (admin.min.js?v=gqomh6ivrjk:2:1072499)
    at j.fn.init.each (admin.min.js?v=gqomh6ivrjk:2:1070979)
    at Se (admin.min.js?v=gqomh6ivrjk:2:1109933)
    at j.fn.init.on (admin.min.js?v=gqomh6ivrjk:2:1116413)
    at j.each.j.fn.<computed> [as change] (admin.min.js?v=gqomh6ivrjk:2:1158537)
    at r.apply.o (admin.min.js?v=gqomh6ivrjk:2:366215)
    at 73461 (admin.min.js?v=gqomh6ivrjk:2:367711)
    at o (admin.min.js?v=gqomh6ivrjk:2:2098741)
    at 32887 (admin.min.js?v=gqomh6ivrjk:2:371401)
    at o (admin.min.js?v=gqomh6ivrjk:2:2098741)
    at admin.min.js?v=gqomh6ivrjk:2:2118709
    at admin.min.js?v=gqomh6ivrjk:2:2118719

@PitaJ it seems (now after two plugin updates to Q&A and Polls) that the front-end issues have disappeared, but the ACP is completely non-functional

Coming from here, perhaps

<baris>

I don't see this Q.uid = 1 on our own admin.min.js so it must be coming from a plugin/theme. For reference you can check our admin.min.js here https://community.nodebb.org/assets/admin.min.js?v=qq8hi2bqamg

Are you sure you tested with just the default plugins? Can you post the output of ./nodebb plugins on the instance you have this issue.

phenomlab

@baris said in Console error after upgrade to 2.1.0:

Are you sure you tested with just the default plugins? Can you post the output of ./nodebb plugins on the instance you have this issue.

Positive. I disabled all plugins in fact, and the issue persists

    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, disabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, disabled)
    * [email protected] (installed, disabled)
    * [email protected] (installed, enabled)
    * [email protected] (installed, enabled)

phenomlab

@phenomlab said in Console error after upgrade to 2.1.0:

For a proof of concept, I completely stripped all plugins, removed the custom JS, Custom CSS, and Custom Header.
Upgraded to 2.1.0 and STILL get the same error message in the ACP console

@baris see this thread

PitaJ

What browser are you using? Have you tried other browsers?

phenomlab

@PitaJ edge. Same in different browsers or incognito. Others have the same issue

<baris>

@phenomlab https://sudonix.dev is your your dev site right? I created an account there, if you give me admin access I can take a look. Maybe I can spot something that is different from this site.

phenomlab

@baris yes, that's my dev site. The issue with giving you admin rights is that I can't access anything in the ACP to do so ! The only way this would work is for me to downgrade the forum, grant you admin, then upgrade again - unless there's a way to do this from the database ?

Edit - ok, done from frontend via groups. Good to go.

<baris>

@phenomlab The issue was with the customize plugin, I disabled it on your forum and the error is gone. I will publish a new version of that once I get access to it. For anyone wondering this is the fix https://github.com/NodeBB/nodebb-plugin-customize/commit/e90dcb9be7c8c3b43715d4dc3310c045615a9998

<baris>

@PitaJ published [email protected]

phenomlab

@baris thanks for this. I can confirm this is now working, but what's really odd here is that previously, the error persisted even with all plugins disabled.

I'm curious to understand if the two plugins I previously referenced that received updates in between me reporting this issue were perhaps part of the issue as with all plugins disabled, the issue persisted. Even clearing all caches did nothing.

Very odd indeed, but thanks for finding the culprit. I've upgraded this plugin, and now everything is working.

<baris>

Well I disabled that plugin and rebuilt all assets just disabling and restarting wouldn't fix it.

phenomlab

@baris Which is exactly what I did ! Very odd, but pleased it's fixed, and hope everyone else can benefit from this. Thanks for all the help.