UI not loading after git pull update

Product Support Self-hosting

AI-generated summary

A user, sindork, experienced issues with their Discourse UI not loading after a git pull update. They tried rebuilding and restarting the server, but the issue persisted. ssvenn suggested visiting the safe mode URL and checking the logs for errors. sindork discovered that the issue was related to an unofficial plugin and disabled it, resolving the problem after rebuilding the app. A minor styling issue with post and topic list borders remained, but was easily fixable with CSS tweaks. Stephen requested that the problematic plugin be identified and tagged as #plugin:broken-plugin if listed in #plugin.

1

Just ran a git pull and rebuild my discourse instance. Webserver is running. Background loads. But there is no UI. Pretty much nothing in the body tags loads. I’ve tried rebuilding the app and restarting my server. Still an issue.

image
image1918×942 58.1 KB

2

Is there any difference if you try

I’ve had some trouble with my theme components after updating recently, it showed up as error messages in /var/discourse/shared/standalone/log/rails/production.log

3

Thanks. This is helping. I tried every combination of the three toggles on the safe mode page. The only combination where it still doesn’t load is when I disable my current theme but don’t disable unofficial plugins or all plugins. Does this mean it could be an issue between an official and unofficial plugin?

I haven't touched the plugins in a while. From my memory, I don't think I was running any unofficial plugins. This is wrong. I’m disabling one plugin at a time and rebuilding to see if I can isolate the issue.

I don’t see the word “error” in either production.log or production_errors.log-20190121 under /var/discourse/shared/standalone/log/rails/

Any ideas?

4

Looks like I did have an old plugin screwing things up. Once I disabled it and rebuilt the app, the site works fine now. Having a minor issue with the color of the borders for the posts and topics list, but that is easily fixed with some css tweaks.

Thanks for the help.

5

If the plugin is listed in Customization > Plugin do let us know which it was, as it may need to be tagged #plugin:broken-plugin.