Client-side vs. server-side?

Product Support

AI-generated summary

In a discussion titled ‘Client-side vs. server-side?’, users explore how Discourse’s safe mode affects plugins. Jagster questions how to distinguish between client-side and server-side plugin components when using safe mode, noting it failed to resolve issues twice due to server-side problems. Moin and JammyDodger clarify that safe mode only disables JavaScript (client-side) portions of plugins, not server-side Ruby code — which requires rebuilding the container with the plugin commented out. Jagster expresses concern about trusting safe mode without deep technical knowledge, fearing false negatives. JammyDodger reiterates that safe mode is partial and advises seeking community help if it doesn’t resolve the issue. Jagster laments the time-consuming process of testing 10+ plugins individually. Arkshine suggests manually disabling plugins one-by-one if logs offer no clues, noting that context often points to the culprit — and that rebuilding can fix many issues, with the community often able to quickly identify root causes.

1

This is pure end-user-level-admin question :woozy_face:

But with safe-mode how do I know which plugins are client-side and therefore off and which ones are server-side and still functional?

2

I think since a plugin can include both JavaScript and Ruby code, it isn’t one or the other.

3

Sure it can, and must. Because that would mean we have one useless option on safe-mode :thinking:

And that has actually happened twice to me. Safe-mode did not help because problematic plugin was server-side.

Or you are talking about different thing. Or I am totally lost. Or both :winking_face_with_tongue:

4

Safe mode disables a portion of the plugin, not all the plugin. So if your issue on that particular day is with the server-side elements then safe mode won’t be as much help.

5

Sorry, I don’t follow you now.

Do you mean that safe-mode doesn’t disable some plugins totally, but only some parts of those?

And if yes then next question is: how can we trust on safe-mode unless one has so much knowledge that can judge when error happends on server-side? I mean if safe-mode doesn’t help how can I know if it is a false negative result?

6

This :point_up:

Like it says here :point_down: :slight_smile:

But if safe mode helps you figure out the problem then :white_check_mark:, if not you can come on here and we can help you figure it out. :slight_smile:

7

Surely I come here because if I have an issue that doesn’t disappear when themes, components and plugins are disabled via safe-mode, I still don’t know if some plugin is issue. Something like 10 plugins and 30 mins rebuilding time per each…

Hopefully I get next time, as it happened last time, something useful from logs.

8

If disabling TC/plugins doesn’t help and you see nothing in /logs, and you have absolutely no clues, I believe you have no choice but to disable plugins one by one until you figure out which one is faulty.

That said, I believe most of the time, you see where it fails or has some context, and you can guess the plugin.

Rebuilding from the console to update everything can also solve many hurdles. The team is pretty fast at fixing issues.

If you are unsure, I would ask the community; you can be sure someone will immediately see the root cause of the issue. :+1: