I’m developing a plugin that will make it easy to connect Discourse installations to any custom app that your organisation may have and deliver push notifications through that app (mainly useful for iOS where webpush doesn’t work). The plugin repository is GitHub - Sprachprofi/discourse-app-notifications: Send Discourse push notifications through FCM to any custom app · GitHub. Right now, this requires the end user to manually paste the device key from the app into a custom field on the Notifications Preferences page after logging in. My problem is that when someone installs the app, logs in and then goes to copy-paste their device key, it doesn’t work, Discourse yields “required plugin ‘discourse_app_notifications’ not found” for the POST /app_notifications/subscribe action (and same for the unsubscribe action). However, when the same person force-quits the app and then does the same step again, there is no error message and the push notifications do work. What could possibly cause Discourse to recognize the plugin in one case and not recognize it in the other case, when the same call is made from within the app? No changes have been made on the Discourse installation in the meantime and this behaviour is consistent and reproducible.

Thank you, @pfaffman . I rewrote the plugin according to the guidelines and it’s working now! New URL: GitHub - Sprachprofi/discourse-fcm-notifications: Send Discourse push notifications through FCM to any custom app · GitHub

This doesn’t necessarily solve your problem, but may cause issues and definitely makes your code harder to navigate for the uninitiated. The structure of your plugin is very unconventional and you should consider refactoring it to match Zeitwerk standards. I’m not sure if that will be causing any of your problems. [image] Structuring a plugin for Rails autoloading Developer Guides Many plugins include lots of class definitions inside plugin.rb, or use require_relative to load ruby files. That works, but it comes with some disadvantages: No auto-reloading of changes in development. Any changes require a full server restart Getting the require calls in the right order can be painful If they are require’d outside the after_initialize block, then other autoloaded classes/modules may not be available There is a solution! Plugins can lean on the standard Rails autoloading sy…

I had a similar problem (though it seemed to be warning and not an error), but making my line like this: plugin.rb 78b689cc4 post '/subscribe' => 'push#subscribe' post '/unsubscribe' => 'push#unsubscribe' end Discourse::Application.routes.append do mount ::DiscourseAppNotifications::Engine, at: '/app_notifications' end require_dependency 'application_controller' class DiscourseAppNotifications::PushController < ::ApplicationController requires_plugin DiscourseAppNotifications::PLUGIN_NAME layout false before_action :ensure_logged_in skip_before_action :preload_json def automatic_subscribe DiscourseAppNotifications::Pusher.subscribe(current_user, params[:token]) if DiscourseAppNotifications::Pusher.confirm_subscribe(current_user) #flash.now[:notice] = "You have successfully subscribed to push notifications." render json: success_json use the PLUGIN_NAME seems to have fixed it. Like Robert said, it might fix some things if you put your controller in app/controllers rather than in plugin.rb. I too was confused where it might be.

I do have requires_plugin DiscourseAppNotifications::PLUGIN_NAME, so I’m not sure which change you’re suggesting, if any? The reason the plugin is structured like this is because I used the Pushover Notifications plugin as a foundation rather than coding from scratch. It’s my first plugin and due to the interaction with the app it’s notoriously difficult to debug, so I was hoping to avoid some bugs this way…

[image] Judith Meyer: I’m not sure which change you’re suggesting, if any? No. It s mostly a shrug. I had the problem, but you seem to have done what I did to fix it. [image] Judith Meyer: I used the Pushover Notifications plugin as a foundation rather than coding from scratch. Sounds like what I would have done. Rails is really picky about a bunch of things. I didn’t know it would let you put that stuff in plugin.rb. And I don’t know if moving stuff to a bunch of different places will fix it. Sorry.

Intermittent "plugin not found" error

Development

pfaffman (Jay Pfaffman) December 12, 2023, 11:17am 7

Glad that worked!

Topic		Replies	Views
Discourse Plugins and Rails 6 config/initializers Question Development	22	3480	November 22, 2020
Developing Discourse Plugins - Part 1 - Create a basic plugin Developer Guides plugin-guides , tutorial	32	85498	July 8, 2025
Discourse Mobile Push — FCM push notifications for mobile apps Plugin	5	241	October 17, 2026
Push Notifications Not functioning Product Support	22	3829	May 3, 2019
Pushover notifications Plugin notifications	21	5113	April 4, 2026

Intermittent "plugin not found" error

Related topics