Barebones install of mojoPortal

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.
11/24/2007 4:07:49 AM
Gravatar
Total Posts 40

Barebones install of mojoPortal

Hi all,

I'd like to install mojoPortal with minimal functionality, adding extra modules, languages etc as and when I need to. Can anyone suggest the easiest way for me to do this? What are the files, folders etc which can safely be left out of the installation?

Thanks,

Matt

11/24/2007 6:55:05 AM
Gravatar
Total Posts 18439

Re: Barebones install of mojoPortal

Hi,

The core features are configured using xml config files under the /Setup/applications/mojoportal-core/FeatureDefinitions folder.

These files point to the module controls for various features, most of which are located in the /Modules folder. You can potentially remove all of the core features and add a feature definiton for only custom features that you create. If the feature is already installed best to manually un-install using the site admin first before physically removing the files. If you remove the files before setting up the site (by visiting siteroot/Setup/Default.aspx, then they won't get installed. Configuration of features happens by visiting the /Setup/Default.aspx page. It looks for these files and configures the features.

So for a concrete example if you don't want the blog to get installed you can delete:

/Setup/applications/mojoportal-core/FeatureDefinitions/20000_BlogModule.config
/Modules/BlogModule.ascx
/BlogView.aspx
/BlogArchiveView.aspx
/BlogCategoryView.aspx
/BlogCategoryEdit.aspx
/BlogEdit.aspx

or you can uninstall and remove them if the site is already setup. Similar process for other features. First uninstall using site admin features under Administration > Features, then physically remove the files. Feature specific supporting pages have the feature name as part of the name so if you want to remove forums you can remove the module control and pages named Forum*.aspx

I recommend that you at least keep the HtmlContent module but its not required either. If you do remove it you should also look at the file(s) in the /Setup/initialcontent/pages folder. Config files there are used to create pages during installation. Since features can be configured on pages in these files you should make sure there aren't any that use features you are excluding.

Hope it helps,

Joe

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