[Admin Note] One of your themes or plugins contains code that needs to be updated

Ondersteuning
1

[Admin Note] One of your themes or plugins contains code that needs to be updated. (ID:discourse.legacy-array-like-object.proxied-array)

Unfortunately, I can’t figure out where the problem is from the browser console either. I had two such messages; one was caused by the Locations plugin, but that disappeared after an update. I’m stuck here.

Affected page: www.xpeng-fahrer.de

2

Do you see any messages in the browser console?

I don’t see any warning in the console. Not even after I registered. It might be an adjustment that only affects administrators.

I’d suggest checking whether the message also appears when you use Safe Mode — first with everything disabled, and if the banner then disappears, disable themes and plugins separately to narrow it down further.

3

I dismissed the message earlier - it only pops up once every 24 hours or so… It doesn’t show up in Safe Mode anymore, but that’s probably because I closed it beforehand.

4

It did indeed. You are welcome. :wink:

5

So this one was caused by your plugin too?

6

But the one I listed above still appears after the Locations plugin update — so, in my opinion, it must be related to something else.

7

Have you tried the plugin update that was released about an hour ago?

8

I’ll give it a try — I’ll let you know if the message shows up again.

9

The related Locations fix was some time ago, April 2nd:

10

If the fix in the Locations plug-in was already back in April, then it’s probably not your issue now.

I’m curious to see what comes up when testing in safe mode.

11

Good morning,

The message is back. In Safe Mode, I unchecked all the boxes one by one — this message does not appear in Safe Mode!

As soon as I started Safe Mode, the error message disappeared — even without Safe Mode. And I didn’t click it away.

12

Can you list the plugins you use?

13

The following are installed and enabled:

https://meta.discourse.org/t/discourse-github/99895https://github.com/discourse/discourse/tree/main/plugins/discourse-lazy-videos

14

Could you add this to your browser console (F12) and hit return:

const LegacyArray = window.moduleBroker.lookup(
    "discourse/lib/legacy-array-like-object"
  ).default;

  const originalWarning = LegacyArray.warnArrayDeprecation;

  LegacyArray.warnArrayDeprecation = function (instance, property) {
    console.trace("Deprecated array access", instance.__type, property);
    return originalWarning.call(this, instance, property);
  };

then, without refreshing, navigate to admin and see if you can cause the notice to appear.

now copy the message you should see in the console here.

15

Unfortunately, the message didn’t come through.

See the screenshot. I clicked through everything in the menu (yes, sometimes a bit too fast).

Could it be related to Locations? I’m currently having an issue with the map’s API key - I did enter the new key, but the map still shows the notification (see screenshot).

Screenshot 2026-09-21 at 21.17.20
Screenshot 2026-09-21 at 21.17.201632×684 223 KB

16

No, I don’t think this is an issue with the Locations plugin - as stated, the fix went out in April - though it is possible I am incorrect.

Try removing Locations and see if the issue goes away completely.

18

@darkpixlz

I don’t know why the posts are being moved.

The error message also appears with the Locations plugin disabled…

19

The base map is provided by Carto and they require an API key since around end of August. It’s free for up to 5 million requests per month:

Screenshot 2026-09-22 at 8.37.18 AM
Screenshot 2026-09-22 at 8.37.18 AM2582×164 27.8 KB

Add the url from Carto with your key into your Location map tile layer field.

20

The posts were moved here from their original support topic.

Do you think the API key will fix the [Admin Notice] One of your plugins or themes contains code that needs updating (ID:discourse.legacy-array-like-object.proxied-array) error he is trying to debug?

I feel like we should focus on that one first. The console output was shared to answer @merefield’s question, not because there was a problem with the locations plugin