Features missing in production server

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
12/22/2009 2:19:47 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Features missing in production server

It sounds like the package you produced is missing a lot of files from under /Setup

you should compare the files in your package with my deployment zip files from the download page and see what is missing in yours and then figure out why they are missing from the way you produce a package.

You have not really told us step by step what you did to produce your package for deployment.

Hope it helps,

Joe

12/22/2009 9:22:10 PM
elopez
Gravatar
Total Posts 6
View Posts

Re: Features missing in production server

Thanks Joe. I've just compared the /Setup folder in my package with the one in your deployment package, and the difference is that my package /Setup folder is heavier because it contains SchemaInstallScripts for all the supported databases while your package only contains SchemaInstallScripts for MSSQL and MYSQL. Everything else is there including mojoportal-core\FeatureDefinitions.

Anyway, I decided to start all over from scratch and just upload your deployment package (and not mine) to my production server. And it all works fine, except that now I don't get to use some custom code I added myself to the VS solution. I'll have to live with it while I figure out how to do it right.

So I probably must have done something wrong in my package, and probably the deployment procedures are under-documented, because I'm telling you I just defined myself to follow the online documentation.

Thanks for your help.

Edwin

You must sign in to post in the forums. This thread is closed to new posts.