제 사이트에서 원인을 알 수 없는 오류가 발생했습니다. 관리자 외의 사용자 또는 사이트 직원은 자신의 개인 메시지를 볼 수 없습니다. 개인 메시지의 제목은 메시지 일반 목록에 표시되지만, 링크를 클릭해도 전체 내용이 열리지 않습니다. 모든 플러그인과 테마 구성 요소를 비활성화해 보았고, 심지어 모든 CSS를 제거해 보았지만 아무런 효과가 없었습니다. 오류 메시지는 다음과 같이 표시됩니다:
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:561:in `block in register_topic_cust
24 Nov 9:33 pm
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:576:in `block in register_user_custo
24 Nov 9:33 pm
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:566:in `block in register_post_custo
24 Nov 9:33 pm
Deprecation notice: add_to_serializer's respect_plugin_enabled argument should be passed as a keyword argument At /var/www/discourse/plugins/discourse-category-lockdown/plugin.rb:21:in `block in acti
24 Nov 9:33 pm
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-custom-wiz
24 Nov 9:33 pm
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-custom-wiz
24 Nov 9:33 pm
Deprecation notice: add_to_serializer's respect_plugin_enabled argument should be passed as a keyword argument At /var/www/discourse/plugins/discourse-ratings/plugin.rb:202:in `block in activate!`
24 Nov 9:33 pm
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-ratings/pl
24 Nov 9:33 pm
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-ratings/pl
24 Nov 9:33 pm
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:556:in `block in register_category_c
24 Nov 9:33 pm
Deprecation notice: The :post_notification_alert event is deprecated. Please use :push_notification instead (deprecated since Discourse 3.2.0.beta1) (removal in Discourse 3.3.0.beta1) At /var/www/dis
24 Nov 9:33 pm
4
ActiveRecord::StatementInvalid (PG::UndefinedColumn: ERROR: column "thread_id" does not exist LINE 1: ..._drafts"."chat_channel_id", "chat_drafts"."data", "thread_id...
24 Nov 10:45 pm
4
Failed to handle exception in exception app middleware : ActiveRecord::StatementInvalid : PG::UndefinedColumn: ERROR: column "thread_id" does not exist LINE 1: ..._drafts"."chat_channel_id", "chat_dr
24 Nov 10:45 pm
17
Clearing Active Record cache, this can happen if schema changed while site is running or in a multisite various databases are running different schemas. Consider running rake multisite:migrate.
24 Nov 10:45 pm
11
ActiveRecord::StatementInvalid (PG::UndefinedColumn: ERROR: column "thread_id" does not exist LINE 1: ..._drafts"."chat_channel_id", "chat_drafts"."data", "thread_id...
24 Nov 10:45 pm
11
Failed to handle exception in exception app middleware : ActiveRecord::StatementInvalid : PG::UndefinedColumn: ERROR: column "thread_id" does not exist LINE 1: ..._drafts"."chat_channel_id", "chat_dr
24 Nov 10:45 pm
3
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
25 Nov 12:49 am
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
25 Nov 12:49 am
24
Can not rebake post# 612 after 3 attempts, giving up : ActiveRecord::RecordNotFound : Couldn't find Topic with 'id'=137 [WHERE "topics"."deleted_at" IS NULL]
25 Nov 1:24 am
24
Job exception: Couldn't find Topic with 'id'=137 [WHERE "topics"."deleted_at" IS NULL]
25 Nov 1:24 am
4
Deprecation notice: add_to_serializer's respect_plugin_enabled argument should be passed as a keyword argument At /var/www/discourse/plugins/discourse-ai-topic-summary/plugin.rb:32:in `block in activ
25 Nov 8:45 pm
5
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:561:in `block in register_topic_cust
25 Nov 8:45 pm
5
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:576:in `block in register_user_custo
25 Nov 8:45 pm
5
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:566:in `block in register_post_custo
25 Nov 8:45 pm
4
Deprecation notice: add_to_serializer's respect_plugin_enabled argument should be passed as a keyword argument At /var/www/discourse/plugins/discourse-category-lockdown/plugin.rb:21:in `block in acti
25 Nov 8:45 pm
4
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-custom-wiz
25 Nov 8:45 pm
4
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-custom-wiz
25 Nov 8:45 pm
4
Deprecation notice: add_to_serializer's respect_plugin_enabled argument should be passed as a keyword argument At /var/www/discourse/plugins/discourse-ratings/plugin.rb:202:in `block in activate!`
25 Nov 8:45 pm
4
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-ratings/pl
25 Nov 8:45 pm
4
Deprecation notice: add_to_serializer should not be used to directly override include_*? methods. Use the include_condition keyword argument instead At /var/www/discourse/plugins/discourse-ratings/pl
25 Nov 8:45 pm
5
Deprecation notice: Array types for custom fields are deprecated, use type :json instead (removal in Discourse 3.3.0) At /var/www/discourse/lib/plugin/instance.rb:556:in `block in register_category_c
25 Nov 8:45 pm
4
Deprecation notice: The :post_notification_alert event is deprecated. Please use :push_notification instead (deprecated since Discourse 3.2.0.beta1) (removal in Discourse 3.3.0.beta1) At /var/www/dis
25 Nov 8:45 pm
298
Sidekiq is consuming too much memory (using: 679.16M) for 'neurogid.com', restarting
25 Nov 11:27 pm
Deprecation notice: the :meta_data param is deprecated, use the :topic_custom_fields param instead (deprecated since Discourse 3.2) (removal in Discourse 3.3) At <internal:kernel>:90:in `tap`
25 Nov 11:37 pm
8
MaxMindDB (/var/www/discourse/vendor/data/GeoLite2-City.mmdb) could not be found: No such file or directory @ rb_sysopen - /var/www/discourse/vendor/data/GeoLite2-City.mmdb
25 Nov 11:44 pm
8
MaxMindDB (/var/www/discourse/vendor/data/GeoLite2-ASN.mmdb) could not be found: No such file or directory @ rb_sysopen - /var/www/discourse/vendor/data/GeoLite2-ASN.mmdb
25 Nov 11:44 pm
16
MaxMindDB (/var/www/discourse/vendor/data/GeoLite2-City.mmdb) could not be found: No such file or directory @ rb_sysopen - /var/www/discourse/vendor/data/GeoLite2-City.mmdb
25 Nov 11:45 pm
16
MaxMindDB (/var/www/discourse/vendor/data/GeoLite2-ASN.mmdb) could not be found: No such file or directory @ rb_sysopen - /var/www/discourse/vendor/data/GeoLite2-ASN.mmdb
25 Nov 11:45 pm
2
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
Su 9:20 am
3
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
Su 3:30 pm
17
Job exception: undefined method `include?' for nil:NilClass
12:24 am
20
OpenAIBot Post Embedding: There was a problem, but will retry til limit: undefined method `destroy!' for nil:NilClass
10:25 am
3
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
11:11 am
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
11:38 am
27
NoMethodError (undefined method `enable_personal_messages?' for SiteSetting:Class) app/serializers/topic_view_details_serializer.rb:127:in `include_can_invite_to?' (eval):11:in `_fast_attributes' lib/
2:20 pm
6
NoMethodError (undefined method `enable_personal_messages?' for SiteSetting:Class) app/serializers/topic_view_details_serializer.rb:127:in `include_can_invite_to?' (eval):11:in `_fast_attributes' lib/
2:20 pm
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
4:22 pm
2
[Telegram Bridge] Failed to bridge message: [1/12] [policy] 'require_plugin_enabled' ✅ [2/12] [contract] 'default' ✅ [3/12] [model] 'channel_id' ❌ [4/12] [policy] 'require_channel_id_vaild' [5/12] [p
5:31 pm
93
Job exception: undefined method `include?' for nil:NilClass
5:58 pm
275
Job exception: undefined method `include?' for nil:NilClass
6:14 pm
다만 개인 메시지(PM)에 영향을 미치는 서드파티 플러그인이 있다면, 그곳부터 시작하는 것이 좋은 출발점이 될 수 있습니다. Pfaffman이 말했듯이, 때로는 안전 모드만으로는 충분하지 않으며 app.yml에서 해당 플러그인을 제거하고 다시 빌드해야 할 수도 있습니다. 현재 사이트에는 어떤 플러그인이 설치되어 있나요?
안녕하세요! 네, 맞습니다 문제는 Custom Trust Level 플러그인으로 인해 발생했습니다. 저희 프로그래머가 여러분과 @pfaffman 님이 조언하신 대로 조치했으며, 훌륭한 지원을 해 주셔서 두 분 모두에게 진심으로 감사드립니다
네, 말씀이 맞을 수 있습니다. 플러그인이 너무 많다는 점을 이해하며, 향후(업데이트 시) 오류가 발생할 수 있음을 인지하고 있습니다. 하지만 저는 AI 관련 새로운 프로젝트를 막 시작하는 단계로, 어떤 플러그인이 제 프로젝트에 실제로 유용할지, 어떤 플러그인은 나중에 필요하지 않을지 파악하기 위해 모든 플러그인을 테스트해 보고 싶습니다.