# Custom component not visible on live enviroment

**URL:** <https://forum.shopware.com/t/custom-component-not-visible-on-live-enviroment/88962>\
**Category:** Shopware 6 (English)\
**Tags:** general, administration\
**Created:** [8. Juli 2021 um 07:25 UTC](https://forum.shopware.com/t/custom-component-not-visible-on-live-enviroment/88962 "2021-07-08T07:25:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rann](https://avatars.discourse-cdn.com/v4/letter/r/7993a0/32.png) [@Rann](https://forum.shopware.com/u/Rann)\
**Post date:** [8. Juli 2021 um 07:25 UTC](https://forum.shopware.com/t/custom-component-not-visible-on-live-enviroment/88962/1 "2021-07-08T07:25:20Z")

</div>

Hi,

I’m probably doing something wrong, but I really don’t see what at the moment.

I’ve created a a plugin on a local enviroment (in dockware), where I can add a custom component in the shopping experience editor.

But when moving this plugin to my live enviroment, install and activate it, my custom component never appears in the back-end.

Also when **not** running the admin-watcher on my dockware, the plugin also does not appear. It’s like some cache isn’t being refreshed…  
But after running build-administration.sh on this enviroment it does appear.

Now I know you shouldn’t run build-administration on a live enviroment, what essential thing am I missing here?

attached a screenshot of the folder structure.

 ![Capture](https://europe1.discourse-cdn.com/flex013/uploads/shopware/original/2X/3/36bc5a7ab17b04530ef3790638a944f7256c52a7.png)

---

<div class="post-metadata">

**Author:** ![Rann](https://avatars.discourse-cdn.com/v4/letter/r/7993a0/32.png) [@Rann](https://forum.shopware.com/u/Rann)\
**Post date:** [8. Juli 2021 um 07:37 UTC](https://forum.shopware.com/t/custom-component-not-visible-on-live-enviroment/88962/2 "2021-07-08T07:37:54Z")

</div>

Haha negate this…

Found out that after rebuilding locally with build-administration.sh, a extra ‚public‘ folder appears in the plugin structure.

Uploaded that, ran asset install, cleared cache, all good!
