Greetings to all forum participants and the Discourse team! An unspecified error has occurred on my site. A user or site employee (except the administrator) cannot see his personal message. The title of a private message appears in the general list of messages, but clicking on the link does not open the full content. I tried disabling all plugins and theme components, even tried removing all CSS, but nothing helped. This is how it is written: [image] This is what is shown when the user tries to refresh the browser page: [image] Here is the console screen: [image]

I think it’s likely the Custom Trust Level plugin. I think someone else had a similar issue with that a little while back: [image] Our PMs stopped working Support It seems I can’t see the 'enable_private_messages" option anymore on our admin panel. Only admin accounts can read PMs. Logs: 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/freedom_patches/ams_include_without_root.rb:57:in `include!' app/controllers/application_controller.rb:551:in `render_json_dump' app/controllers/topics_controller.rb:1332:… You (or your developer) would need to remove that plugin from your app.yml and rebuild without it. Hopefully that should make everything come good. :crossed_fingers:

There may be more detail if you check your /logs page. Could you check in there and paste the info here in a code block?

Did you disable the plugins via the settings or remove them from the yml and rebuild? If you didn’t remove and rebuild, you should do that.

[image] JammyDodger: /logs Sorry for the long response :pray: That’s all there was: 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 :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

[image] Jay Pfaffman: Did you disable the plugins via the settings Yes, I disabled plugins through the admin settings.

Ideally, you would need to click on the specific error relevant to the issue and copy the message to paste here. A likely one could be: 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/ Though if you have any third-party plugins that affect PMs then that would be a probable place to start. As Pfaffman says, sometimes safe mode isn’t enough and you would have to remove the plugin from your app.yml and rebuild. What plugins do you have on your site?

[image] Aizada M: Yes, I disabled plugins through the admin settings. That is not sufficient to completely disable many plugins. You need to comment them out in your app.yml and rebuild. [image] Aizada M: 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 That’s going to be a problem, but likely isn’t yet. [image] Aizada M: ActiveRecord::StatementInvalid (PG::UndefinedColumn: ERROR: column "thread_id" does not exist LINE 1: ..._drafts"."chat_channel_id", "chat_drafts"."data", "thread_id... [image] Aizada M: 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. Are you running multisite? Do you have the old chat plugin installed (it has now been merged into core). You should include the list of plugins that you’re using.

[image] JammyDodger: What plugins do you have on your site? Here are the plugins that have been installed on the website: [image] [image] [image] [image] [image] [image] Similarly, @pfaffman, I am not a programmer myself, and I may incorrectly interpret some of your words. Therefore, I decided to share the link to this topic with my programmer.

36 plugins is a lot. Be aware that even if they’re disabled they can still have an impact on your site. When your developer is implementing this fix I would also recommend having them comment out any plugin which isn’t active and in use.

FWIW, I think our Business plan comes bundled with around 31 (all #official though, so probably less of a worry).

[image] JammyDodger: I think it’s likely the Custom Trust Level plugin. Hello! Yes, you were right :100: The problem was caused by the Custom Trust Level plugin. Our programmer did as you and @pfaffman advised, very grateful to both of you for the excellent support :pray: [image] Stephen: 36 plugins is a lot. Yes, you may be right, I understand that there are too many plugins and in the future (during any updates) errors may occur. But, I’m just starting a new project with AI and I want to test all the plugins in order to understand which of them will be really useful for my project, and which ones I won’t need later.

The user cannot see his personal message

Product Support

Aizada_M (Aizada M) November 28, 2023, 1:40pm 8

Here are the plugins that have been installed on the website:

Similarly, @pfaffman, I am not a programmer myself, and I may incorrectly interpret some of your words. Therefore, I decided to share the link to this topic with my programmer.

Topic		Replies	Views
Our PMs stopped working Product Support	4	687	August 12, 2023
Allow sending Private Messages to Staff Feature	16	3451	July 27, 2020
Deprecation notice - SiteSetting.enable_personal_messages Product Support deprecation	2	708	March 20, 2023
Private Topics Plugin Plugin	104	8068	April 22, 2026
Privacy plugin that makes it more difficult for admins to read PMs Feature personal-messages	55	7724	February 6, 2018

The user cannot see his personal message

Related topics