שגיאת HTTP 500 בדף הפורום הראשי לאחר שדרוג Discourse

סיכום מבוסס בינה מלאכותית

After upgrading their Discourse forum, lubezniy encountered an HTTP 500 error on the main page, with logs pointing to a custom field access issue: TopicEventStartsAt. The admin panel worked fine, suggesting a plugin-related problem. The user listed 27 active plugins, including discourse-solved. justin acknowledged the issue and identified a problematic commit in the discourse-solved plugin (6123f22), which was subsequently reverted. After rebuilding the container, lubezniy confirmed the error was resolved. The site affected is https://club.klerk.ru/ tot.

Hello,

We have upgraded our forum today to the latest version, but got HTTP error 500 at the root page. The following message appears in the production.log file inside the container when the root page opens with error 500:

Started GET “/” for 141.8.142.82 at 2021-08-25 21:44:06 +0000
Processing by CategoriesController#index as /
Completed 500 Internal Server Error in 163ms (ActiveRecord: 0.0ms | Allocations: 23021)
StandardError (Attempted to access the non preloaded custom field ‘TopicEventStartsAt’. This is disallowed to prevent N+1 queries.)
app/models/concerns/has_custom_fields.rb:173:in []' lib/plugin/instance.rb:284:in public_send’
lib/plugin/instance.rb:284:in block (2 levels) in add_to_class' (eval):47:in _fast_attributes’
lib/freedom_patches/ams_include_without_root.rb:57:in include!' app/controllers/categories_controller.rb:61:in block (2 levels) in index’
app/controllers/categories_controller.rb:40:in index' app/controllers/application_controller.rb:397:in block in with_resolved_locale’
app/controllers/application_controller.rb:397:in with_resolved_locale' lib/middleware/omniauth_bypass_middleware.rb:71:in call’
lib/content_security_policy/middleware.rb:12:in call' lib/middleware/anonymous_cache.rb:353:in call’
config/initializers/008-rack-cors.rb:25:in call' config/initializers/100-quiet_logger.rb:23:in call’
config/initializers/100-silence_logger.rb:31:in call' lib/middleware/enforce_hostname.rb:23:in call’
lib/middleware/request_tracker.rb:187:in `call’

I have tried to rebuild the container, but the problem not disappeared. The admin page works without any problems. What should we do to repair the forum?

We are using the following plug-ins (all worked correctly before upgrade completion):

      - git clone https://github.com/discourse/docker_manager.git
      - git clone https://github.com/angusmcleod/discourse-quick-messages.git
      - git clone https://github.com/davidtaylorhq/discourse-whos-online.git
      - git clone https://github.com/discourse/discourse-adplugin.git
      - git clone https://github.com/Toxuru/discourse-sidebar-categories.git
      - git clone https://github.com/pmusaraj/discourse-sidebar-blocks.git
      - git clone https://github.com/discourse/discourse-tooltips.git
      - git clone https://github.com/discourse/discourse-saved-searches.git
      - git clone https://github.com/davidtaylorhq/discourse-telegram-notifications.git
      - git clone https://github.com/discourse/discourse-calendar.git
      - git clone https://github.com/discourse/discourse-push-notifications.git
      - git clone https://github.com/joebuhlig/discourse-mlm-daily-summary.git
      - git clone https://github.com/discourse/discourse-solved.git
      - git clone https://github.com/discourse/discourse-hamburger-theme-selector.git
      - git clone https://github.com/discourse/discourse-user-notes.git
      - git clone https://github.com/angusmcleod/discourse-question-answer
      - git clone https://github.com/discourse/discourse-cakeday.git
      - git clone https://github.com/discourse/discourse-yearly-review.git
      - git clone https://github.com/discourse/discourse-subscriptions.git
      - git clone https://github.com/discourse/discourse-signatures.git
      - git clone https://github.com/discourse/discourse-sitemap.git
      - git clone https://github.com/merefield/discourse-user-network-vis.git
      - git clone https://github.com/discourse/discourse-reactions.git
      - git clone https://github.com/discourse/discourse-automation.git
      - git clone https://github.com/discourse/discourse-assign.git

our site https://club.klerk.ru/

We’re aware and looking into it! Looks like it might be a bugged commit causing the issue.

We’ve identified a commit on Solved that may have been causing a conflict.

https://github.com/discourse/discourse-solved/commit/6123f224124a86989763ab5c84f0c5b7faaf68f0

It’s been reverted so please try rebuilding and let us know if you continue to have problems.

Thank you very much. We have no errors now.