TypeError: Cannot set property deleteTopic of [object Object] which has only a getter

Support
1

I have a long standing installation of Discourse that seems to be getting js errors.

Uncaught (in promise) TypeError: Cannot set property deleteTopic of [object Object] which has only a getter
    at ye (index.js:1641:1)
    at y (mixin.js:281:1)
    at w.apply (mixin.js:482:1)
    at e.proto (core.js:600:1)
    at new y (core.js:91:1)
    at new e (core.js:371:1)
    at e.create (core.js:385:1)
    at h.create (index.js:385:1)
    at index.js:287:1
    at index.js:230:1
    at i.lookup (index.js:125:1)
    at u.lookup (container_proxy.js:19:1)
    at m.s (index.js:2075:1)
    at index.js:1310:1
    at validator.js:635:1
    at pe.get (index.js:1309:1)
    at m.r [as topic] (index.js:881:1)
    at Te (index.js:1682:1)
    at reference.js:164:1
    at reference.js:125:1
    at validator.js:622:1
    at d (reference.js:124:1)
    at reference.js:162:1
    at reference.js:125:1
    at validator.js:622:1
    at d (reference.js:124:1)
    at De (index.js:1806:1)
    at ze.create (index.js:1974:1)
    at Object.evaluate (runtime.js:2676:1)
    at Object.evaluate (runtime.js:1052:1)
    at It.evaluateSyscall (runtime.js:4204:1)
    at It.evaluateInner (runtime.js:4175:1)
    at It.evaluateOuter (runtime.js:4168:1)
    at Wt.next (runtime.js:4999:1)
    at Wt._execute (runtime.js:4986:1)
    at Wt.execute (runtime.js:4979:1)
    at Qt.sync (runtime.js:5046:1)
    at hr.<anonymous> (index.js:4672:1)
    at index.js:4934:1
    at Nt (runtime.js:4080:1)
    at gr._renderRoots (index.js:4916:1)
    at gr._renderRootsTransaction (index.js:4960:1)
    at gr._renderRoot (index.js:4905:1)
    at gr._appendDefinition (index.js:4830:1)
    at gr.appendOutletView (index.js:4820:1)
    at invoke (backburner.js.js:282:1)
    at h.flush (backburner.js.js:197:1)
    at p.flush (backburner.js.js:358:1)
    at B._end (backburner.js.js:798:1)
    at backburner.js.js:523:1
application.js:155 TypeError: r.subscribe is not a function
    at d.setupController (topic-from-params.js:94:21)
    at d.setup (route.js:444:1)
    at o (router_js.js:1544:1)
    at s.routeEnteredOrUpdated (router_js.js:1554:1)
    at s.setupContexts (router_js.js:1500:1)
    at s.finalizeTransition (router_js.js:1408:1)
    at router_js.js:1347:1
    at _ (rsvp.js:434:1)
    at y (rsvp.js:420:1)
    at invoke (backburner.js.js:282:1)
    at h.flush (backburner.js.js:197:1)
    at p.flush (backburner.js.js:358:1)
    at B._end (backburner.js.js:798:1)
    at backburner.js.js:523:1
error @ application.js:155
router.js:1141 Error while processing route: topic.fromParamsNear r.subscribe is not a function

A stack trace showing a system error with a black background. (Captioned by AI)
A stack trace showing a system error with a black background. (Captioned by AI)988Ă—515 92.8 KB

I have a cascading set of js errors as a result. When I go to a particular topic, it just shows the error, something went wrong, screen.

Any suggestions on troubleshooting? Thanks in advance.

1 Like
2

Hi @etc :wave: did you check safe mode yet?

when you say “long standing” - I assume you mean longtime functional; but has it been updated to latest version recently?

3 Likes
3

I’ll check out safe mode, thanks.

Yes, long standing as in it’s been functional for years. I was on 3.1, then I posted a reply and then started running into the errors. I upgraded to the latest version just to see if it would fix, but even though the update worked properly, the issue persists.

4

Thanks for the link, it is helping me narrow it down.

So, the option Disable all client-side plugin customizations ended up fixing it. Do you have some documentation on what precisely that is referring to? Thank you! <3 Happy New Year, btw

1 Like
5

So, we’re pretty light on plugins, but it looks like it’s the Discourse-Encrypt plugin, which I believe is an official plugin. When I disable it, everything works, once I reenable it, everything goes down again. Not sure why this would happen out of nowhere.

1 Like
6

This plugin is deprecated, you may want to uninstall it read the topic for instructions.

2 Likes
7

I’ll go ahead and uninstall it. I wonder if something flipped as of Jan 1 that would break the plugin. It seemed to have happened out of nowhere. Thanks so much! Happy New Year!

2 Likes