Community Server - How to install Community Server to a web site?
Community Server - Where can you find additional support?
DotNetNuke - How to install DotNetNuke to a web site?
DotNetNuke - How to install a custom module?
DotNetNuke - Where can you find additional support?
nGallery - Where can you find additional support?
nGallery - How to retrieve or update username/password information?
osCommerce - How to install osCommerce Storefront to a web site?
osCommerce - Configure osCommerce to work with shared SSL and private SSL certificates
 

Community Server is the award winning platform for rapidly enabling online communities and includes all the integrated tools, such as discussion forums, email lists, newsgroups, weblogs (blogs), file galleries, content management, and more to help enable you to create your community presence quickly and easily!

NOTE: You will need to have a MSSQL database with your hosting package in order to install Community Server to your web site.

1. Log into your zeWEBHOST control panel and navigate to Website/Domain Management -> domain.com -> Script Installation -> Community Server.
2. On the "Script Configuration" page, you will need to select a 'MSSQL Database' to work with.
3. When the page reloads, Select a 'MSSQL User' to use for the database.
4. Enter the email address that community server will email from, a username, and password for Community Server.
5. Hit "Set Up Community Server". Community Server can take up to two minutes to install.
 

NOTE: Community Server is a third party product in which limited support is offered by zeWEBHOST. Application support for Community Server should be directed to communityserver.org/forums . Additional documentation can be found at http://docs.communityserver.org/.

1. Community Server Administrator's Guide : A guide to Community Server for administrative users. This guide covers both basic and advanced features as well as how to use the new Control Panel features in version 2.1.
http://docs.communityserver.org/Administrator_s_Guide/Users_Guide_Topics.htm

2. Community Server User's Guide : A smaller guide for non-administrative users that covers some Community Server features related to the blogs and forums applications.
http://docs.communityserver.org/User_s_Guide/Users_Guide_Outline.htm

3. How-To's: A guide on how to create skins/themes for Community Server, including blog themes and forum skins.
http://docs.communityserver.org/How-To_s/Creating_Skins/SkinningTopics.htm

4. FAQ : Provides answers to frequent questions about Community Server. Note: The FAQ's for Community Server 2.1 are still under development and will be updated periodically according to questions we receive about the 2.1 release.
http://docs.communityserver.org/FAQ/FAQTopics.htm

5. Additional Features & Add-Ons: Documentation for additional modules and features available with Community Server such as Custom Authentication modules, Email (SMTP) Gateway, News (NNTP) Gateway, and Enterprise Search.
http://docs.communityserver.org/Additional_Features_And_Add-Ons/AddOnsTopics.htm
 

You can Install DotNetNuke to your web space Using the Script installation tool In your zeWEBHOST Hosting control Panel.

NOTE: You will need to have a MSSQL database with your hosting package in order to install DotNetNuke to your web site.

1. Log into your zeWEBHOST control panel and navigate to Website/Domain Management -> domain.com -> Script Installation -> DotNetNuke.
2. On the "Script Configuration" page, you will need to select a 'MSSQL Database' to work with.
3. When the page reloads, Select a 'MSSQL User' to use for the database.

The DotNetNuke ADMIN login can modify content, layout, and basic settings for your default DotNetNuke portal.
4. Enter your DotNetNuke ADMIN login information:
     a.) Email Address:
     b.) Username:
     c.) Password:

The DotNetNuke HOST login has the same capabilities as the ADMIN login, but can also administer more technical settings of your DotNetNuke installation, and manage all DotNetNuke portals on your Web site.
5. Enter your DotNetNuke HOST login information:
     a.) Email Address:
     b.) Username:
     c.) Password:

6. Click on the 'Set Up DotNetNuke' button to complete the installation. DotNetNuke can take up to two minutes to install.
 

Below are the most common steps for installing a new DotNetNuke module. Custom modules may also come with their own installation documentation.

1. Log into your DotNetNuke site using your Host username and password.
2. On the Menu bar, you will see a section for 'Host'.
3. Go to the host menu and select the 'Module Definitions'.
4. Here you can see the list of the pre-installed modules. At the top left corner (and on the bottom of the page) there is a drop down menu, where you will be able to see "Upload Module" link.
5. Browse to the folder where your module is located and select the package you want to upload. Then click on the "Upload New File" link.

DotNetNuke will report any errors with the installation during this process. If no errors have been reported, the module has been successfully installed and can be assigned to any page using the 'Module' drop-down list

Further information can be found on the DotNetNuke Community Forums at http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/Default.aspx
 

NOTE: DotNetNuke is a third party product in which limited support is offered by zeWEBHOST. Application support for DotNetNuke should be directed to the DotNetNuke forums at http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/Default.aspx.

Additional development tools can be found at http://www.dotnetnuke.com/Development/DeveloperTools/tabid/472/Default.aspx
 

NOTE: nGallery is a third party product in which limited support is offered by zeWEBHOST. Application support for nGallery may be found at the following resources:

1. The nGallery support site at http://www.ngallery.org/support.aspx

2. The nGallery Forums at 'http://www.CommunityServer.org'.
     Search the forums to see if anyone has had a similar issue. The problem you're having may have already been resolved.

3. The nGallery ASP.NET user forums at http://forums.asp.net/129/ShowForum.aspx
 

When you install the nGallery application on your web space using the zeWEBHOST hosting control panel please remember that the login credentials are stored in a configuration file named ngallery.config in your web space.

If at any point you need to retrieve or update your login information for nGallery you can do so by editing the configuration file.

1. Connect to your website via FTP.
2. Locate the file at directory 'http:www.yourdomain.com/ngallery/data/ngallery.config'.
3. Open the file using any text editor program (such as Notepad) and locate and update the following two lines of code:

     <AdminUserName>username</AdminUserName>
     <AdminPassword>password</AdminPassword>

By default, the above code will be located on lines 14 and 15 of the ngallery.config file.

4. Save the updated file to the server, and you will be able to login to nGallery using your updated username/password.
 

You can use the Script installation Utility located in the zeWEBHOST control panel to install osCommerce storefront.

To install osCommerce storefront to your web space follow these steps:

1. Log into your zeWEBHOST control panel and navigate to Website/Domain Management -> domain.com -> Script Installation -> OSCommerce Storefront.
2. On the "Script Configuration" page, you will need to select a 'MySQL Database' to work with.
3. Enter the OSCommerce administrator information.
     Name:
     Email:
     Username:
     Password:

NOTE: This information will be used to set up the administrative section of the OSCommerce application.

4. Click the Set Up OSCommerce to install OSCommerce storefront. OSCommerce may take up to two minutes to install.

If the application was installed successfully you will receive a confirmation page. This page will also contain the links to the administrative section of the application along with the login credentials that you will need to use in order to enter the administrative section so you can set up the application.
 

Before you begin you will need to determine the URL for your Shared SSL site. If your domain can be accessed from:
     http://www.yourdomain.com

Then the secure address for your website is:
     https://secureX.hcpanel.com/yourdomain (X is a number based on the webserver you are on.)

You can determine which secure server you are on by looking at the address bar in your browser after logging into the hosting control panel; it is the number after the first word "secure". So for example, if your domain was yourdomain.com and you were on secure14.hcpanel.com, the address to the secure version of your website would be https://secure14.hcpanel.com/yourdomain.

Configure osCommerce to work with your Shared SSL site:

1. Open the file "configure.php" in your "oscommerce/includes" directory.
2. Change the following lines as shown:

     define('ENABLE_SSL', true);
     define('HTTP_SERVER', 'http://yourdomain.com');
     define('HTTPS_SERVER', 'https://secureX.hcpanel.com/yourdomain');
     define('HTTP_COOKIE_DOMAIN', 'yourdomain.com');
     define('HTTP_COOKIE_PATH', '/oscommerce/');
     define('HTTPS_COOKIE_PATH', '/oscommerce/');
     define('DIR_WS_HTTP_CATALOG', '/oscommerce/');
     define('DIR_WS_HTTPS_CATALOG', '/oscommerce/');

3. Browse to http://yourdomain.com/oscommerce/admin and enter the username and password that you provided during the Script Installation.
4. Go to "Configuration"
5. Click "Sessions" on the left navigation bar.
6. Click "Force Cookie Use", and then click the Edit button on the right hand side. The display should now change to two radio buttons, one labeled True, and one labeled False. Choose the False option and click the Update button.

Your osCommerce installation is now setup to work with our Shared SSL configuration. This will protect your customer's sensitive data while it is in transit to our servers.

NOTE: If you are using a Private SSL certificate, you should update the osCommerce configuration file a follows:

1. Open the file "configure.php" in your "oscommerce/includes" directory.
2. Change the following lines as shown:

     define('ENABLE_SSL', true);
     define('HTTP_SERVER', 'http://yourdomain.com');
     define('HTTPS_SERVER', 'https://www.yourdomain.com');
     define('HTTP_COOKIE_DOMAIN', 'yourdomain.com');
     define('HTTP_COOKIE_PATH', '/oscommerce/');
     define('HTTPS_COOKIE_PATH', '/oscommerce/');
     define('DIR_WS_HTTP_CATALOG', '/oscommerce/');
     define('DIR_WS_HTTPS_CATALOG', '/oscommerce/');
 

To Top