#Fork the admin panel

14 messages · Page 1 of 1 (latest)

mortal hatch
#

Can i fork the admin panel and have my changes and link it to original backend so that my code picks up the plugins as well.

Admin Extensions in Plugins: If you use plugins that provide admin extensions (such as widgets or UI routes), these are typically included in the admin build process when using the standard Medusa monorepo setup. If you fork the admin panel and run it as a standalone project, you will need to ensure that your forked admin is able to discover and include these extensions. The knowledge sources do not provide explicit details on how to automatically pick up admin extensions from backend plugins in a forked admin setup, so you may need to manually integrate or import the relevant components from your plugins into your forked admin project.

Has anyone have done this?

dawn spade
#

yes thats possible i have done it ..

bitter sluice
#

hey @dawn spade do you mind sharing your approach?

drifting raven
#

@dawn spade would love to hear it out

dawn spade
#

let me know if you have any question i will answer and update the guide..

mortal hatch
#

I would love to try this out. Thanks for sharing 🔥 @dawn spade

bitter sluice
mortal hatch
#

I was so close!! Thank you @dawn spade

dawn spade
#

Perfect I’m glad that it worked please comment under the discussion of you experience with this guide .. so others can see

thin tendon
#

Is it possible to use this method to fork a dashboard and use that specifically for vendor panel?

mortal hatch
dawn spade
#

Yes but I wound not do that, you can easily give them ie vendor permission and allow them to see portion of the admin panel ..

eternal needle
#

Does anyone know that after forking, everything worked fine but after upgrading to 2.10.1, I cannot use Draft orders properly whether I install it or not. The built-in admin panel can be used normally. Is it a problem with the version of the forked dashboard?