# Intermittent "plugin not found" error

**URL:** https://meta.discourse.org/t/intermittent-plugin-not-found-error/287181
**Category:** Development
**Created:** [December 1, 2023, 11:43am UTC](https://meta.discourse.org/t/intermittent-plugin-not-found-error/287181 "2023-12-01T11:43:46Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [December 1, 2023, 12:03pm UTC](https://meta.discourse.org/t/intermittent-plugin-not-found-error/287181/2 "2023-12-01T12:03:45Z")

</div>

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.

> [@Structuring a plugin for Rails autoloading](https://meta.discourse.org/t/structuring-a-plugin-for-rails-autoloading/256092):
>
> 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…

---

_[View the full topic](https://meta.discourse.org/t/intermittent-plugin-not-found-error/287181)._