I've been developing a module on my dev machine and trying to publish it to a production machine's Orchard/Modules folder. For the most part this works and I can enable the new module on the Orchard instance on the production machine. I can even add the
Content Part to a Content Type. It's when I go to create a new Content Item of that Content Type that I'm having problems.
The editor template for the Content Part is not showing up like it does on my dev machine. It doesn't error out or anything, it just doesn't show the View for the Content Part's editor. If I hit save it complains that the fields for the custom Content Part
are required, so I can't save it.
I deleted the module from the production server and then FileZilla'd the module to it and it works fine. Is this expected behavior forcing me to keep my modules open source or something? I don't mind the source being open on the server, I just like the ease
of publishing from VS since this module is only specific to my website and not for public consumption.