# Custom plugin isn't displayed after update

**URL:** <https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055>\
**Category:** Self-hosting\
**Created:** [April 27, 2023, 10:11am UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055 "2023-04-27T10:11:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![greeen\_way](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/greeen_way/32/293459_2.png) [@greeen\_way](https://meta.discourse.org/u/greeen_way)\
**Post date:** [April 27, 2023, 10:11am UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055/1 "2023-04-27T10:11:42Z")

</div>

Hello! We tried to update only our custom plugin, but update button was disabled, so we’ve decide to update Docker Manager (because only it has active update button). Once we’ve done it, Discourse and our plugin have automatically updated, but our plugin disappeared from main page (it is enabled in plugins setting bar). May the update of Discourse trigger this behaviour? (we haven’t update it for a long time)

---

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [April 27, 2023, 12:04pm UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055/2 "2023-04-27T12:04:02Z")

</div>

Docker manager updates block any other updates.

Is it possible your custom plugin is no longer compatible?

---

<div class="post-metadata">

**Author:** ![greeen\_way](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/greeen_way/32/293459_2.png) [@greeen\_way](https://meta.discourse.org/u/greeen_way)\
**Post date:** [April 27, 2023, 12:05pm UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055/3 "2023-04-27T12:05:05Z")

</div>

how could I check is it compatible?

---

<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:** [April 27, 2023, 1:01pm UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055/4 "2023-04-27T13:01:49Z")

</div>

1. Run a rebuild from the command line and look for error messages?
2. When on the website, check the javascript console for errors that might be related.

---

<div class="post-metadata">

**Author:** ![greeen\_way](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/greeen_way/32/293459_2.png) [@greeen\_way](https://meta.discourse.org/u/greeen_way)\
**Post date:** [April 27, 2023, 2:14pm UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055/5 "2023-04-27T14:14:25Z")

</div>

1. As soon as I know, there are no error messages during rebuild - sysadmin confirms that plugin is on and running
2. There are no error messages in website console neither

---

<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:** [April 27, 2023, 2:52pm UTC](https://meta.discourse.org/t/custom-plugin-isnt-displayed-after-update/263055/6 "2023-04-27T14:52:26Z")

</div>

Then I think you are going to have to get into the weeds.

Create a dev instance and add some print statement and use console prints (e.g. `pp`), byebug and debugger to follow the progress of the code.