Thanks for your response however exporting from studio will only give you your customisation a and not the base package needed to build the module. This is usually obtained from module builder using publish or export. I however have deleted my module builder packages thinking to was best practice but now believe that I need them in order to build my production environment.
Am wanting to know if there is another way to build the base package so I can export my customisations from studio?
When you delete a package from module builder. Sometimes it doesn’t actually delete the files.
You could build a package manually. Using your favourite file manager. go into custom/modulebuilder/builds/[package_name]. This is essentially where the files are kept.
All you need to do is create a compressed .zip file of the[package name] folder’s contents. Don’t compress the folder rather compress it’s contents. As the manifest.php must be in the root level.
Then you can go into admin->module loader. Then upload the newly created zip file. This will give you package back.
Hey that’s awesome it worked a treat! Thanks heaps for your help!
Just to help the next person who reads this:
HOW TO TRANSFER A CUSTOM MODULE TO A NEW ENIVIRONMENT AFTER YOU HAVE DELETED THE MODULE BUiLDER PACKAGE
Using your favourite file manager. go into custom/modulebuilder/builds/[package_name] of your first environment
This is essentially where the files are kept.
Create a compressed .zip file of the[package name] folder’s contents.
Don’t compress the folder rather compress it’s contents. As the manifest.php must be in the root level.
go into admin->module loader of your second environment
upload the newly created zip file
Install the package
Go to studio in you first environment
Export or publish the customisations for the module