Web Hosting and Domain registration Knowledgebase
msgbartop
Gossimer’s Premier Web Hosting and Domain Registration Knowledgebase.
msgbarbottom

03 Sep 10 Installing osCommerce

Follow the below mentioned process to install the osCommerce Power Tool on your website:

1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>

2. In the search results view, click on the domain name. This will take you to the Order details view.

3. Click on the Manage Web Hosting Service button in the lower toolbar.

4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
 

IMPORTANT

If you have already installed the osCommerce Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.

 

5. In order to install osCommerce, click on Install link under the Status column.

6. In order to install the osCommerce Power Tool you would need to simply input the following details -

i. Database Name – select the database from the drop-down list.
 

IMPORTANT

osCommerce is a database-driven Power Tool. Hence, your hosting package needs to include at least one database. If a database is not included in your current hosting package, the following steps need to performed -

  1. You need to upgrade your package by adding a database. Click here to read how to upgrade your package >>

  2. You need to configure your database. Click here to read how to configure your database >>

ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
 

iii. Database User’s Password – provide the password of the Database User, you selected above.
 

IMPORTANT

The Database User’s Password you input above has to match the Password you entered while adding this User in the Database Manager interface. In the event that you can not recall this Database User’s Password, you need to reset the same before continuing. Click here to find instructions on how to reset the Password of a Database User >>
 

iv. Directory Name – you need to input a new sub-directory name where you want the osCommerce Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
 

IMPORTANT

Confirm that you have sufficient Web Space and Database Space before continuing the osCommerce installation, by referring the information provided in the interface.

Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
 

7. Click on the Install button to complete the osCommerce installation.

 

Besides the above information, you need to provide a few details about the osCommerce Administrator:

1. Admin Name – This is the name of the person who will be administering the osCommerce installation.

2. Password – This is the Administrator’s Password.

3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.

4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the osCommerce Power tool.

Once osCommerce is installed, you can click on the View link under the Details column, to view the details related to osCommerce.
 

IMPORTANT

URL of the osCommerce Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php

URL of the osCommerce Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in osCommerce - eCommerce Shopping Cart Solution with 0 Comments

31 Aug 10 .NET API Kit and Integration Guide

Follow the instructions below to begin integration with the API using .NET.

Make sure you have read the General API Integration Instructions first. If you have already integrated the .NET API Kit at your end, read the Change Log first to know what has changed since.

Reference:

General API Integration Instructions >>
Change Log >>

Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).

Option 1 – Setup Application

 

NET_Core_Setup_v3_10.zip
NET_Domains_Setup_v3_10.zip
NET_Hosting_Setup_v3_10.zip
NET_OtherProducts_Setup_v3_10.zip

 

Option 2 – Compressed ZIP File

NET_CoreExamples_v3_10.zip
NET_DomainsExamples_v3_10.zip
NET_HostingExamples_v3_10.zip
NET_OtherProductsExamples_v3_10.zip
 

 

Step 2. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application (updated on 6th March, 2008).

Core_Docs_v3_10.zip
Domains_Docs_v3_10.zip (updated on 1st April, 2008)
Hosting_Docs_v3_10.zip
OtherProducts_Docs_v3_10.zip
 

Step 3. Install the API Kit
There are two ways by which you may install the API Kit on your computer:

Option 1 – Setup Application
We recommend that you download, unzip and run the setup file. First, however, please be sure that you have administrator privileges to install applications on the computer. If you’re hosting your website with a third-party provider and do not have the rights to install applications, then you will not be able to use the setup application to install the kit. Therefore, you may manually install and use the required API files from our compressed ZIP file option (Refer to Option 2 below).

The setup application will perform the following tasks:

     

  1.  A .NET dll containing the kit, and the relevant documentation, will be placed inside your “Program Files” folder; by default, the path would be “C:Program Files”. Therefore, you should be able to find the DLL and the documentation corresponding to your kit. Please ensure that you have the .NET runtime installed before you attempt to use the API kit.

  2. Relevant shortcuts will be placed in your start menu.

  3.  If you have Microsoft Internet Information Server version 5.0 or greater (IIS) installed, the setup file will create a virtual directory named as OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples in your “Default Web Site”. The setup file allows you to give the virtual directory any name of your choice. This virtual directory contains a Visual Studio .NET project called OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples, which illustrates every function provided in the OrderBox API. You may run the examples by either by:

    • Opening it in Visual Studio.Net and pressing the F5 key, or

    • Visiting the url http://localhost/examples/ in your browser.

 


Option 2 – Compressed ZIP File
Download the zip file and extract the files to any temporary folder. The temporary folder will now contain the following subfolders:

     

  1. OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples – The folder contains the example files to illustrate every method in the kit.
     

  2. bin – This folder contains the actual kit DLL file. This is a .NET DLL, and requires the .NET runtime to be pre-installed, for use.

 


Installing the examples on your own computer:

     

  1. Create the Examples folder (OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples) inside the root of any website configured in IIS, on your computer. IIS contains a default website called “Default Web Site”, having it’s root folder set to “c:Inetpubwwwroot”. If you have a default installation of IIS, you would create a subfolder called “examples” inside that root folder. Please note that you may name the examples directory as you please, you are not restricted to the name OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples.
     

  2. Open the IIS management console by navigating to “Start > Programs > Administrative Tools > Internet Information Services”
     

  3. Now, we need to create an “Application Root” for the examples folder. This can be accomplished by opening the properties window for that directory and clicking on the “Create” button.

 

If you successfully completed the above steps, you may open your browser and point it to http://localhost/examples (if you gave your examples folder some other name, replace the last word of the URL with that name).
 

Step 4. Run the examples
Please note first that the ASP.NET examples are provided solely to help illustrate usage of the ASP.NET Kit. You may use the example files directly, or simply use them as a reference project while developing your application to interface with the OrderBox API.
 

IMPORTANT  

IIS 5.0 and the .NET runtime MUST be installed on your machine, BEFORE you run the kit setup file.

 

 


After you’ve installed the ASP.NET examples, open your browser, and point it to “http://localhost/your-examples-folder” (you may use the name given to the examples folder to replace “examples” in the preceding url). This shall open the ASP.NET examples webpage, which is divided into three frames:

  • The frame on the top allows you to mention the Service URL, your Reseller Username, your Password, ParentID, Language Preference, Role, Debug Mode to make API calls independent of the credentials provided in the APIConstants.vb file. This frame also provides you a checkbox to enable/disable the credentials of this frame. That is, if the checkbox is not selected the APIConstants.vb file credentials will be used to make the API call.
     

  • The lower left frame contains a list of links to pages that illustrate the use of each method in the API. When you click a link, it’s corresponding page is displayed in the right hand side frame. You may test the functions by putting in the call parameters in the page.
     

 

Step 5. Understanding Errors
Make sure you have read the General API Integration Instructions to obtain links to the error format and possible error documents. Reference: General API Integration Instructions >>
 

Step 6. Writing your own code
The API classes exist within the namespace OrderBoxCoreLib , OrderBoxDomainsLib, OrderBoxHostingLib, OrderBoxOtherProductsLib. The class named “Properties”, contains static variables useful for debugging, and changing the SOAP End Point.

The following are valid end points for the OrderBox Demo Server:

  • HTTP DEMO SERVICE URL: “http://api.onlyfordemo.net/anacreon/servlet/APIv3-XML”

  • HTTPS DEMO SERVICE URL: “https://api.onlyfordemo.net/anacreon/servlet/APIv3-XML”

The following are valid end points for the OrderBox Live Server:

  • HTTP LIVE SERVICE URL: “http://www.myorderbox.com/anacreon/servlet/APIv3-XML”

  • HTTPS LIVE SERVICE URL: “https://www.myorderbox.com/anacreon/servlet/APIv3-XML”

Example: To test the examples, you must first create an account on the Demo server. To use the Customer webservices of the OrderBox API, instantiate the customer object as demonstrated below. If at any time the SOAP end point must be changed to some other url, you may simply put the new SOAP end point into this variable.

Properties.Url = “http://soap-end-point”;

The following code instantiates the Customer object. You may now use it’s methods to call various OrderBox API functions. These are SOAP calls, that will be made to the SOAP End Point specified by the Propeties.Url variable.

Customer oCustomer = new Customer ();

To illustrate the use of this object, we shall take the example of a method called getCustomerId. Examine the code snippet below. It uses an object of the Customer class to request the id of a specified username.

int result = 0; 

// First we make sure that our SOAP End Point is pointing to the correct resource.
Properties.Url = “http://api.onlyfordemo.net/anacreon/servlet/APIv3-XML“;

// The examples use a class called Constants, containing static properties that hold your credentials. You may set these properties once, and later in the file simply pass them to the method calls as required. The values set below are simply examples, and must be replaced with your own credentials.
Constants.Username = “username@domain.com”; // Your username goes here.
Constants.Password = “your-password”; // Your password goes here.
Constants.Role = “reseller”; // Your role goes here.
Constants.LangPref = “en”; // Your language preference goes here.
Constants.ParentID = 1; // Your parent id goes here.

// Since we wish to view the soap request and response …
Properties.Debug = true;

// Next we instantiate an object of the Customer class.
Customer oCustomer = new Customer ();

// We then use this customer object to request the id for a specified username.
result = oCustomer.getCustomerId (ApiConstants.SERVICE_USERNAME,
ApiConstants.SERVICE_PASSWORD,
ApiConstants.SERVICE_ROLE,
ApiConstants.SERVICE_LANGPREF,
ApiConstants.SERVICE_PARENTID,
“username”);

// Now we display the soap request.
Console.WriteLine (Properties.getLastRequest); Console.WriteLine ();

// Then we display the soap response.
Console.WriteLine (Properties.getLastResponse); Console.WriteLine ();

// Lastly we display the result.
Console.WriteLine (result);

The above code accepts authentication details and a username, and returns an integer value, which is the id corresponding to the username passed. The last parameter of the getCustomerId method is the username for which we requested an id. This id was returned into the integer variable result.

Please note the first five parameters of this method call. They consist of the username, password, role, language preference, and parent id respectively, of the individual calling the method. For the examples, you may make a demo account on the demo server, and pass the username, password, role, language preference and parent id from your demo account to this method call. These are the first five parameters that are passed to every API call that is undertaken. Please make sure that you pass accurate details for these parameters. If you do not, your method call will be unsuccessful.

IMPORTANT 

In registering/managing any domain name on the demo server always use ns1.onlyfordemo.net and ns2.onlyfordemo.net as your nameservers. ANY OTHER Nameserver will result in an INVALID NAMESERVER error.

 

 

Step 7. Change the information to Live information when you are ready
When you have got the examples working correctly, you may set the value of Properties.Url to one of the live URL’s, and pass your own authentication details when making API calls.

 

 

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in .NET API Kit with 0 Comments

29 Aug 10 Debugging Perl/CGI Scripts

Hosting servers are configured to store error logs for CGI/Perl scripts, encountered during the course of operation. By default, error messages are sent to STDERR.

Most HTTPD servers direct STDERR to the server’s error log, which stores information for all the websites hosted on a shared hosting environment. As this, this file cannot be accessed by individual website owners. You may wish to keep private error logs, distinct from the server’s error log, or  may wish to direct error messages to to a web browser.

This can be accomplished by coding your scripts accordingly during the development phase.

Sending error messages to a private log file

The carpout() function can be used to achieve this. Since carpout() is not exported by default, you must import it explicitly as -

use CGI::Carp qw(carpout);
 

The carpout() function requires one argument, which should be a reference to an open filehandle for writing errors. It should be called in a BEGIN block at the top of the CGI application so that compiler errors will be caught. Example:

BEGIN {
use CGI::Carp qw(carpout);
open(LOG, “>>/domains/domain.com/logs/cgi-error.log”) or
die(“Unable to open cgi-error.log: $!n”);
carpout(LOG);
}
 

carpout() does not handle file locking on the log for you at this point.

Sending error messages to a Web Browser

Fatal (die, confess) errors can be sent to a web browser by importing the special “fatalsToBrowser” subroutine:

use CGI::Carp qw(fatalsToBrowser);
die “Couldn’t open log file”;
 

Fatal errors will now be echoed to the browser as well as to the log file. CGI::Carp arranges to send a minimal HTTP header to the browser so that even errors that occur in the early compile phase will be seen. Nonfatal errors will still be directed to the log file only (unless redirected with carpout).

 

Sample Script

#!/usr/bin/perl -wT

# In the first line above, T causes Perl to check
# for “tainted” data, that is, data from outside the
# script (i.e. user input) that is going to be used
# to affect something else outside the script
# (i.e. writing to a log file)

# You can untaint data by parsing it for unwanted
# characters then saving it to another variable.

# If you are having trouble with a script, try removing
# the T switch to see if that is the problem.

# The w switch in the first line causes warnings about
# script syntax to be printed, if there are any.

# This script does 2 things:
#
#1. It directs fatal errors to the browser,
# so when the script is invoked via the Web,
# a meaningful error message is returned.
# This is useful when developing a script;
# but should be disabled when the script
# is made publicly available.
#
# 2. It will direct any error message the script
# generates to an error log that resides in
# the user’s home directory. The file must
# already exist and be “other” writeable.

# Notice that the following is enclosed in a BEGIN { }
# block that causes it to execute before the rest of
# the script is read.

# This block should be placed in the main script,
# as near the top as practical. Do not place it in
# subroutines or libraries. Always test
# subroutines thoroughly before placing them
# in libraries.

BEGIN {

# define an error log in YOUR home directory
# this is an example where the
# home directory is /domains/domain.com/

my $error_log = “/domains/domain.com/logs/cgi-error.log”;

# “my” in the line above makes the variable $error_log
# local so it only has meaning inside this block.
# See your text for more on variable scope.

# load the CGI::Carp module;
# fatalsToBrowser directs fatal errors to the browser
# carpout is for directing errors to the error log

use CGI::Carp qw(fatalsToBrowser carpout);

open (LOG,”>>$error_log”) ||
die “couldn’t open log file: $!”;
carpout(LOG);

# open(…) is used to open a file.
# >> means the new input will be appended what’s
# already in the file.

# LOG is a nickname (properly called a “file handle”)
# that is given to the file so it is easy to refer to
# it later, i.e. carpout(LOG) sends the error
# message to the file with the nickname LOG

# || means “or” (as in do this or that)
# die means stop executing the program. You can add
# a message in quotes after the die command.

# $! is a special variable that contains the current error info

}

# The following line will cause an error.
# It is a call to a sub-routine that does not exist.
# After you have tried this script and received the error message,
# comment out the following line so no error occurs
# and “Hello world!” is printed.

&non_existent_subroutine();

print <<EOT;
Content-type: text/htmlnn

<HTML>
<BODY>
Hello world!
EOT

print “</BODY></HTML>”;

Tags: , , , , , , , , , , , , , , , , , , ,

Filed in Linux Hosting related Caveats with 0 Comments

27 Aug 10 Sub-Domain Forwarding

How does Gossimer, LLC Sub-Domain Forwarding work?

Using the Sub-domain forwarding service, you can forward any visitor from http://subdomain.your-domain-name.com/ to http://destination-domain-name.com/subdomain/. The Sub-Domain Forwarding service can also be used in conjunction with URL Masking and Path Forwarding services.

For example, if Sub-Domain Forwarding is enabled, then:

  1. http://payments.your-domain-name.com will get successfully forwarded to http://destination-domain-name.com/payments/
     

  2. http://credit-card.payments.your-domain-name.com will get forwarded to http://destination-domain-name.com/payments/credit-card/
     

Enabling / Disabling Sub Domain Forwarding

You can enable / disable Sub-Domain Forwarding after you have bought Domain Forwarding for a particular Domain Name. You need to follow the steps mentioned below to activate the same:

  1. Login to your Control Panel and search for the domain name.
     

  2. Click on the Domain name in the search results to get to the Order Details view.
     

  3. Upon clicking on Manage Service, selecting the check box enables Sub-Domain Forwarding, while deselecting the same disables this feature.

Tags: , , , , , , , , , , , , , , , ,

Filed in Managing a Domain Forwarding Service with 0 Comments

27 Aug 10 Installing phpBB

Follow the below mentioned process to install the phpBB Power Tool on your website:

1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>

2. In the search results view, click on the domain name. This will take you to the Order details view.

3. Click on the Manage Web Hosting Service button in the lower toolbar.

4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.

IMPORTANT

If you have already installed the phpBB Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.

5. In order to install phpBB, click on Install link under the Status column.

6. In order to install the phpBB Power Tool you would need to simply input the following details -

i. Database Name – select the database from the drop-down list.

  1. You need to upgrade your package by adding a database. Click here to read how to upgrade your package >>

  2. You need to configure your database. Click here to read how to configure your database >>

ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.

iii. Database User’s Password – provide the password of the Database User, you selected above.

The Database User’s Password you input above has to match the Password you entered while adding this User in the Database Manager interface. In the event that you can not recall this Database User’s Password, you need to reset the same before continuing. Click here to find instructions on how to reset the Password of a Database User >>

iv. Directory Name – you need to input a new sub-directory name where you want the phpBB Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).

IMPORTANT

Confirm that you have sufficient Web Space and Database Space before continuing the phpBB installation, by referring the information provided in the interface.

Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>

IMPORTANT

IMPORTANT

phpBB is a database-driven Power Tool. Hence, your hosting package needs to include at least one database. If a database is not included in your current hosting package, the following steps need to performed -

7. Click on the Install button to complete the phpBB installation.

Besides the above information, you need to provide a few details about the phpBB Administrator:

1. Admin Name – This is the name of the person who will be administering the phpBB installation.

2. Password – This is the Administrator’s Password.

3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.

4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the phpBB Power tool.

Once phpBB is installed, you can click on the View link under the Details column, to view the details related to phpBB.

IMPORTANT

URL of the phpBB Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php

URL of the phpBB Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in phpbb - bulletin board system with 1 Comment

26 Aug 10 Direct Download Manager

The Direct Download Manager is another feature exclusive to the Gossimer Control Panel. It helps you save several hours of your valuable time by allowing you to download files to your web space directly from another server via a HTTP URL or FTP URL.

If you need to transfer large files to your web space that are already available on some other server, then you would typically have to download these files locally to your desktop and re-upload them. All of this could take up quite some time depending on the file size and your Internet connection speed. However, using the server-to-server transfer facility provided by the Direct Download Manager, you can utilize the server’s high speed connection to directly download large files. So, even if you are connected to the Internet via a dial-up connection, file transfers will occur at the very high speeds. 

This feature is most useful when you are transferring your Website data from your previous Web Hosting provider, as you could just zip up your whole website and instead of downloading it locally to your desktop, directly download it on the server and unzip it there. 

Using the Direct Download Manager
Follow the process mentioned below to download files using the direct download manager:

1. Login to your Control Panel and search for the domain name for which you have purchased this hosting package.

2. In the search results view, click on the domain name. This will take you to the order details view.

3. Click on Manage Web Hosting Service in the lower toolbar.

4. In the Website Management interface pop-up that follows, go to Manage Website -> Additional Tools -> Direct Download Manager.

5. Here, provide the following details

  • The remote URL – i.e., the location of the file that you wish to download
  • Destination – the directory to which you wish to send the downloaded file

6. Click on Download Now. This would download the file to the location you have specified.

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in Linux Hosting Specific Features with 0 Comments

25 Aug 10 How to Troubleshoot Delays in Displaying your SuperSite/PartnerSite Pages?

 

In the event that you notice some delay in displaying content on your SuperSite/PartnerSite, Gossimer allows you to pinpoint the cause for this delay, through a nifty tool. If you are not able to troubleshoot the reason for this lag through this tool, we would request you to forward Gossimer the output of this tool at support@gossimer.com.

 

Enabling this tool

 

There are two ways in which you can enable this tool on your SuperSite/PartnerSite:

1. You may enable this tool from your SuperSite/PartnerSite URL by submitting the following URL, and then navigate over to the page that is taking time to load

http://<Your SuperSite URL>/?show_profiler=true
http://<Your PartnerSite URL>/?show_profiler=true

2. You may also visit the page which is taking time to load and enable this tool directly from that page, by submitting the URL, as displayed in the following example -

http://<Your SuperSite URL>/somepage.php?show_profiler=true
http://<Your PartnerSite URL>/somepage.php?show_profiler=true

However if the URL already has some parameters being passed to it through “&”, then you need to enable this tool by submitting the URL as displayed in the following example -

http://<Your SuperSite URL>/somepage.php?action=promos_amp;show_profiler=true
http://<Your PartnerSite URL>/somepage.php?action=promos_amp;show_profiler=true

IMPORTANT 

  • When you enable this tool for your SuperSite/PartnerSite, then the results of this tool are displayed only to you.
  • Your SuperSite/PartnerSite continues to be displayed normally to other people.

Upon enabling this tool, you would notice results such as the following, at the very bottom of that page -

Sample Output

============================================================================
PROFILER OUTPUT
============================================================================
Calls Time Routine
—————————————————————————–
1 4.2040 ms ( 0.26 %) common/footer/footer.html
1 3.9160 ms ( 0.24 %) common/header/header.html
1 2.2640 ms ( 0.14 %) common/header/includes/change_language.html
1 9.7451 ms ( 0.59 %) common/header/includes/header_cart.html
1 3.5040 ms ( 0.21 %) common/header/includes/header_dashboard.html
1 3.5779 ms ( 0.22 %) common/header/includes/header_logindiv.html
1 2.5790 ms ( 0.16 %) common/header/includes/static_bar_under_menu.html
1 0.2789 ms ( 0.02 %) footer
1 159.7109 ms ( 9.70 %) getCountryCodeForIP
1 414.6559 ms ( 25.18 %) getResellerDetailsFromURL
1 3.3398 ms ( 0.20 %) header
1 22.2020 ms ( 1.35 %) homepage/index.html
1 3.5648 ms ( 0.22 %) promos/sidebar_promo_blurb.html
1 7.3581 ms ( 0.45 %) root.html
1 14.2081 ms ( 0.86 %) sidebars/sidebar.html
…

In the bottom, you will see something like this:

1 82.7694 ms ( 5.03 %) unprofiled

838.3358 ms ( 50.90 %) Missed
============================================================================
1647.0261 ms (100.00 %) OVERALL TIME
============================================================================

 

 

Disabling this tool

Once you have noted the complete output of this tool (as displayed above), you should disable it. This can be disabled in any one of the following ways:

1. You may disable this tool from your SuperSite/PartnerSite URL

http://<Your SuperSite URL>/?show_profiler=false
http://<Your PartnerSite URL>/?show_profiler=false

2. You can visit any page and disable this tool from that page, by submitting the URL, as displayed in the following example -

http://<Your SuperSite URL>/somepage.php?show_profiler=false
http://<Your PartnerSite URL>/somepage.php?show_profiler=false

However if the URL already has some parameters being passed to it through “&”, then you need to disable this tool by submitting the URL as displayed in the following example -

http://<Your SuperSite URL>/somepage.php?action=promos_amp;show_profiler=false
http://<Your PartnerSite URL>/somepage.php?action=promos_amp;show_profiler=false
 

 

IMPORTANT 

Once you close your browser window, this tool gets automatically disabled.
 

 

 

Tags: , , , , , , , , , , , , , ,

Filed in SuperSite and PartnerSite Caveats with 0 Comments

22 Aug 10 How do I Add/Edit a SuperSite/PartnerSite Theme or How do I edit the CSS, Images, Javascript of my SuperSite/PartnerSite?

Gossimer allows you the ability to completely change the look and feel of your SuperSite and PartnerSite through the use of Themes.
 

What is a Theme?


A Theme is a set of design elements and color schemes that you apply to pages to give them a consistent and attractive appearance. Using a Theme is a quick and easy way to add interest to pages and give them a professional look.

A Theme allows you to alter the appearance of your SuperSite/PartnerSite by modifying its:

  • Cascading Style Sheets. By tweaking individual CSS files in your Theme you can modify the fonts, colors, spacing, etc., being displayed on your SuperSite/PartnerSite.
     
  • Images. You can replace the default set of images within your SuperSite/PartnerSite Theme. This is especially useful when you have translated your SuperSite/PartnerSite content and would want to display images with embedded text in that language.
     
  • Javascript. The style of the Javascript Menu within your SuperSite/PartnerSite Theme can be equally easily modified, to suit your customized SuperSite/PartnerSite.

By applying a Theme you can immediately apply a predetermined set of design elements to your SuperSite/PartnerSite content. When you choose one theme to be the default theme for your website, the theme is applied to all existing pages and to new pages that you add later.
 

How to Add/Modify a Theme or How do I edit the CSS, Images, Javascript of my SuperSite/PartnerSite?

 

IMPORTANT 

     

  1. To modify the CSS, Images and Javascript of your SuperSite/PartnerSite, you need to first add a NEW Theme.
     
  2. While adding a Theme, you need to select the Default Theme from where you want the default CSS, Images and Javascript to be initially loaded. As you modify these elements, your changes become a part of your new Theme.

 

Adding a Theme

You can create your own Themes using the default Theme as mentioned below -

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
      

    IMPORTANT 

    The Default SuperSite/PartnerSite Theme cannot be edited. If you wish to change the look and feel of your SuperSite/PartnerSite, you need to create your own Theme and modify the same.

     

     

  3. In order to create your own Theme, click on the Create Custom Theme link on the top right-hand corner of this page.
     
  4. Provide a unique name for your Theme and click Create My Theme. The Theme thus created will be listed under Your SuperSite/PartnerSite Theme(s) section.
     
  5. Click on the Browse link next to the Theme to view the contents of the Theme.
     
  6. Here you will find folders for CSS (Cascading Style Sheet) files, Images and JavaScript files.
     

    7.  

 

Modifying your Theme (editing your SuperSite/PartnerSite CSS, Images, Javascript)

 

You can modify the CSS files (Cascading Style Sheets) for different sections of SuperSite and PartnerSite, by following the process outlined below:

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Now click on Browse next to the CSS folder.
     
  5. This interface lists all the sections. Click on Browse, adjacent to the section for which you wish to modify the style sheets.
     
  6. The following page lists all the CSS files used in the section you have chosen. Click on Edit, adjacent to the CSS file you wish to modify.
     
  7. You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
     
  8. Click on the Save Changes button beneath after completing the modification.
     
IMPORTANT 

If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.

 

 

Virtually every image in SuperSite and PartnerSite is customizable – should you not find any to your liking, you can replace it with another at any time.
 

IMPORTANT 

     

  1. In order to modify an image file in SuperSite or PartnerSite, you need to note its name. To get the name of the image, simply right-click on the image in your browser, and select Properties. Here, you would find the address for the image. For example, http://<prefix>.SuperSite/PartnerSite.myorderbox.com/getImage.php?src=image-name.gif, or

    http://<prefix>.partnersite.myorderbox.com/getImage.php?src=image-name.gif

    where image-name.gif is the name that you require.
     

  2. Also, there are some image files which are a part of the CSS itself; you would not be able to retrieve the filenames in the above manner. To retrieve the names of such image files, you need to check the style sheets for the section containing the image in question, and retrieve the image file name from there. Click here to find instructions on how to edit your SuperSite/PartnerSite/PartnerSite CSS files >>
     
  3. : You can follow the process mentioned below to replace the default header logo with the logo of your company. To do so, you need to replace the image named yourbrand.gif.

 


Follow the process outlined below to modify any Image files in your SuperSite/PartnerSite:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Click on Browse link next to the Images folder.
     
  5. This interface lists all the images used by the SuperSite/PartnerSite.
     
  6. In the list, look for the name of the image you wish to modify. Click on Edit, adjacent to it.
     
  7. Click on Browse, and select the image you wish to upload in place of the default.
     
  8. Click on Upload Image. This will replace the default Image with the one you have provided, such that every page where the old image file was being displayed, would now display your uploaded image file.

    9.  

 

 

In addition to the default images, you can add/edit your own images as mentioned below:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Click on Browse link next to the Images folder.
     
  5. Click on Browse next to the MyUploadedImages folder.

    6.  

 

Adding your own Images

     

  1. Click on the Add your own Images button on the top right-hand corner of this page.
     
  2. Click on Browse, and choose the image that you want to upload.
     
  3. Once the image is selected, click on Upload button.

Editing Images added by you

     

  1. Click on the Edit link next to the image you wish to modify.
     
  2. Click on Browse, and choose the image that you want to upload.
     
  3. Once the image is selected, click on Upload Image button.

After uploading an image using the above tool, you would need to link it from some HTML page on your SuperSite/PartnerSite.

IMPORTANT 

     

  1. If you have translated your SuperSite/PartnerSite content to multiple languages, then you may want to have images with text embedded on them in that particular language itself. To accomplish this you would need to associate different languages to separate Themes and within each Theme have Images related to only that language.
     
  2. If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.

    3.  

The manner in which the menu is displayed, can be modified just as easily:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Click on Browse next to the JS folder.
     
  5. Click on Edit, adjacent to the menu_style.js file.
     
  6. You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
     
  7. Click on the Save Changes button beneath after completing the modification.

    8.  

IMPORTANT  


 How do I apply a Theme to my SuperSite/PartnerSite?
 

You can display your SuperSite/PartnerSite in either the Default Theme provided by Gossimer or use any one of the Themes you have recently added. Follow the below mentioned process to accomplish this:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Configure Languages and Themes link.
     
  3. Here you may either set your Theme for the Default English Language or any other language added by you, by selecting the Theme from the Associated Themes drop-down.
     
  4. Click on the Save button to associate the selected Theme to a particular language.
     

    5.  

 

IMPORTANT 

The Theme you have selected will be applied to your SuperSite/PartnerSite ONLY after you have enabled that particular language.

 


 Click here to know how to configure Multiple Language support to your SuperSite/PartnerSite >>

Tags: , , , , , , , , , , , , , , , , , ,

Filed in How do I customize the Content, Theme (CSS, Images, Javascript), HTML Structure of the SuperSite and PartnerSite? with 0 Comments

22 Aug 10 Installing WordPress

Follow the below mentioned process to install the WordPress Power Tool on your website:

1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>

2. In the search results view, click on the domain name. This will take you to the Order details view.

3. Click on the Manage Web Hosting Service button in the lower toolbar.

4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.

IMPORTANT

If you have already installed the WordPress Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.

5. In order to install WordPress, click on Install link under the Status column.

6. In order to install the WordPress Power Tool you would need to simply input the following details -

i. Database Name – select the database from the drop-down list.

IMPORTANT

WordPress is a database-driven Power Tool. Hence, your hosting package needs to include at least one database. If a database is not included in your current hosting package, the following steps need to performed -

  1. You need to upgrade your package by adding a database. Click here to read how to upgrade your package >>

  2. You need to configure your database. Click here to read how to configure your database >>

ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.

iii. Database User’s Password – provide the password of the Database User, you selected above.

IMPORTANT

The Database User’s Password you input above has to match the Password you entered while adding this User in the Database Manager interface. In the event that you can not recall this Database User’s Password, you need to reset the same before continuing. Click here to find instructions on how to reset the Password of a Database User >>

iv. Directory Name – you need to input a new sub-directory name where you want the WordPress Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).

IMPORTANT

Confirm that you have sufficient Web Space and Database Space before continuing the WordPress installation, by referring the information provided in the interface.

Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>

7. Click on the Install button to complete the WordPress installation.

Besides the above information, you need to provide a few details about the WordPress Administrator:

1. Admin Name – This is the name of the person who will be administering the WordPress installation.

2. Password – This is the Administrator’s Password.

3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.

4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the WordPress Power tool.

Once WordPress is installed, you can click on the View link under the Details column, to view the details related to WordPress.

IMPORTANT

URL of the WordPress Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php

URL of the WordPress Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in wordpress - personal publishing software with 0 Comments

22 Aug 10 Installing PHP-Nuke

 

Follow the below mentioned process to install the PHP-Nuke Power Tool on your website:

 

1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>

2. In the search results view, click on the domain name. This will take you to the Order details view.

3. Click on the Manage Web Hosting Service button in the lower toolbar.

4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
 

IMPORTANT

If you have already installed the PHP-Nuke Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.

 

 

5. In order to install PHP-Nuke, click on Install link under the Status column.

6. In order to install the PHP-Nuke Power Tool you would need to simply input the following details -

 

 

i. Database Name – select the database from the drop-down list.
 

 

 

IMPORTANT

PHP-Nuke is a database-driven Power Tool. Hence, your hosting package needs to include at least one database. If a database is not included in your current hosting package, the following steps need to performed -

 

 

  1. You need to upgrade your package by adding a database. Click here to read how to upgrade your package >>

  2. You need to configure your database. Click here to read how to configure your database >>

 

ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
 

iii. Database User’s Password – provide the password of the Database User, you selected above.
 

 

 

IMPORTANT

 

The Database User’s Password you input above has to match the Password you entered while adding this User in the Database Manager interface. In the event that you can not recall this Database User’s Password, you need to reset the same before continuing. Click here to find instructions on how to reset the Password of a Database User >>
 

 

iv. Directory Name – you need to input a new sub-directory name where you want the PHP-Nuke Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
 

IMPORTANT

Confirm that you have sufficient Web Space and Database Space before continuing the PHP-Nuke installation, by referring the information provided in the interface.

Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
 

 

 

7. Click on the Install button to complete the PHP-Nuke installation.

 

Besides the above information, you need to provide a few details about the PHP-Nuke Administrator:

1. Admin Name – This is the name of the person who will be administering the PHP-Nuke installation.

2. Password – This is the Administrator’s Password.

3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.

4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the PHP-Nuke Power tool.

Once PHP-Nuke is installed, you can click on the View link under the Details column, to view the details related to PHP-Nuke.
 

IMPORTANT

URL of the PHP-Nuke Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php

URL of the PHP-Nuke Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php

 

 

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in php nuke - news publishing system with 0 Comments

19 Aug 10 PHP API Kit and Integration Guide

Follow the instructions below to begin integration with the API using PHP -

Make sure you have read the General API Integration Instructions first. If you have already integrated the PHP API Kit at your end, read the Change Log first to know what has changed since.

Reference:

General API Integration Instructions >>
Change Log >>

IMPORTANT   

The PHP API Kit is not compatible with version PHP5. You need to use version PHP4 in order to integrate the API Kit at your end.

 

 

Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).

PHP_CoreKIT_v3_10.zip
PHP_DomainsKIT_v3_10.zip
PHP_HostingKIT_v3_10.zip
PHP_OtherProductsKIT_v3_10.zip

Step 2. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application (updated on 6th March, 2008).

Core_Docs_v3_10.zip
Domains_Docs_v3_10.zip (updated on 1st April, 2008)
Hosting_Docs_v3_10.zip
OtherProducts_Docs_v3_10.zip

 

IMPORTANT  

Since “list” is a keyword in the PHP language, the “list()” methods in the various classes (in the PHP Kit) has been renamed to “listOrder().” However, the documentation still mentions the method name as “list” since the documentation is JAVA specific.

 

 

 

Instructions to pass parameters to functions using the PHP Kit

Since PHP uses typeless variables you will have to ignore the datatypes presented in the docs. But for assigning values to variable of types other than strings and integers special care will have to be taken. Below is the list of datatypes presented in the API Doc and their usage in PHP.

Java Data

Types Assigning values in PHP
String “firstname@secondname.com”
int 123
HashMap (Datatype for storing name-value pair) array(“domain.com”=>”1″)
Array and Vector (Datatype for storing more than one value) array(“ns1.domain.com”,”ns2.domain.com”)
boolean (Datatype for storing true or false) true / false

Example:

  • For Calling a Function which takes a String datatype and an integer datatype as its paramters

    public int function1(java.lang.String userName, int parentid)
    $result = $obj->function1(“firstname@secondname.com”,1);
     

  • For Calling a Function which takes a HashMap, a String Array and an integer Array as its parameters

    public java.util.HashMap function2(java.util.HashMap domainHash, java.lang.String[] orderby, int[] resellerId)

    and domainHash is accepting the domainname and the number of years as name value pair

    $result = $obj->function2(array(“domain1.com”=>1,”domain2.com”=>2),array(“column1″,”column2″),array(22,33))
     

  • For Calling a Function which takes a Vector and a boolean as its parameters

    public java.lang.String function3(java.util.Vector nameServers, boolean add)
    $result = $obj->function3(array(“ns1.domain.com”,”ns2.domain.com”),true)

 

Step 3. Extract the files from the API Kit archive
You should get the following directory & files structure

examples/ – Pre-written examples. You can directly run these examples to test API functionality
lib/ – The PHP class files, library files and wsdl files that you need to run your application
 

Step 4. Run the examples
You can run the pre-written examples provided in the “examples” folder. Note the following steps to do so -

1. Upload the “examples” and “lib” folders to your web server where you run your PHP scripts. Make sure that both these folders are uploaded to the same parent folder.

2. You must have PHP 4 installed on the server

3. You must have a Demo account ready the first time. Read the General instructions if you have not yet setup your demo account. Reference: General API Integration Instructions >>

IMPORTANT   

The Demo server duplicates all functionality of the live server, however all Domain Names will appear as available on the Demo Server. It does not query the live registry and therefore names which are not available on the live registry will still appear as available on the Demo Server. At times connectivity to the DEMO Registry may be down resulting in errors.

 

4. Make the appropriate changes to “constants.php” in the “examples” folder, by putting in the values for your “SERVICE_USERNAME”, “SERVICE_PASSWORD”, “SERVICE_PARENTID”. The remaining settings have already been made for you in this file. You may only need to change the path for the “lib” folder if you have uploaded the lib folder elsewhere

5. The URL to which the call is made is maintained in the “config.php” file inside the “lib” folder. By default all calls are made to the demo server URL using HTTP. You can make changes to this file and redirect your calls to the appropriate server

IMPORTANT   

If you are using HTTPS calls you MUST have the extension for CURL installed and enabled in your PHP installation.

 

6. Another important parameter maintained in the “config.php” file is the variable $DEBUG. If this variable is set to “true”, then for each call you will see the entire XML Request and Response in the output. You should keep it to “true” during testing, but set it to false on the live environment.

7. Every Example file has a set of functions which you can run.

8. Once you have modified the appropriate example file, access it over your webserver by putting in your URL such as http://yourserver/examples/html and choose the required function from the links given in the left frame.

IMPORTANT   

In registering/managing any domain name on the demo server always use ns1.onlyfordemo.net and ns2.onlyfordemo.net as your nameservers. ANY OTHER Nameserver will result in an INVALID NAMESERVER error.

 

Step 5. Understanding Errors
Make sure you have read the General API Integration Instructions to obtain links to the error format and possible error documents. Reference: General API Integration Instructions >>
 

Step 6. Writing your own code
After running each example above, if you simply refer to the corresponding .php file in the examples folder you will easily be able to figure out the code snippet you need to write in order to make a similar call.

Making an API call to perform any action is a matter of three steps:

(i) Include the appropriate PHP Class file as below

include($LIB_DIR.”Order.class.php”);

(ii) Obtain a pointer to the required Class. This is done by using the code below

$serviceObj = new Order($LIB_DIR . “wsdl/Order.wsdl”);

(iii) Call the required method on this object. A complete reference of all methods is available in the Docs folder. This can be achieved by using the code below

$AssociativeArray = $serviceObj->setCustomerLock($SERVICE_USERNAME, $SERVICE_PASSWORD, $SERVICE_ROLE, $SERVICE_LANGPREF, $SERVICE_PARENTID, $orderId);

IMPORTANT   

You will notice above that EVERY method in the docs takes the same first 5 parameters as below

String SERVICE_USERNAME, String SERVICE_PASSWORD, String SERVICE_ROLE, String SERVICE_LANGPREF, int SERVICE_PARENTID

 

In the examples these parameters have been put into a single constants file from which they are accessed by including the constants file. These parameters are common no matter which method you call. These parameters mean the following:

String SERVICE_USERNAME: Your Username
String SERVICE_PASSWORD: Your Password
String SERVICE_ROLE: This will always be a string "reseller"
String SERVICE_LANGPREF: The 2 letter code of the language in which you wish to receive errors and descriptions - "en" for English
int SERVICE_PARENTID: The ID of your parent which you can get from your profile section

IMPORTANT   

Remember, when passing numerical data in hashtables, please ensure that the number is passed as a String.


Step 7. Change the information to Live information when you are ready
Once you have followed the steps above and got the test examples to work successfully, you can duplicate the same code in your live application and replace the Demo Server and Reseller account information with your live username and password. The URL that you make your calls to also needs to change to the LIVE Server URL. You will make this change in the “config.php” file in the “lib” folder

Once again note, if you are using the HTTPS URL you MUST have the extension for CURL installed and enabled in your PHP installation.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Filed in PHP API Kit with 0 Comments

18 Aug 10 How do I Add/Edit a SuperSite/PartnerSite Theme or How do I edit the CSS, Images, Javascript of my SuperSite/PartnerSite?

Gossimer allows you the ability to completely change the look and feel of your SuperSite and PartnerSite through the use of Themes.

What is a Theme?

A Theme is a set of design elements and color schemes that you apply to pages to give them a consistent and attractive appearance. Using a Theme is a quick and easy way to add interest to pages and give them a professional look.

A Theme allows you to alter the appearance of your SuperSite/PartnerSite by modifying its:

  • Cascading Style Sheets. By tweaking individual CSS files in your Theme you can modify the fonts, colors, spacing, etc., being displayed on your SuperSite/PartnerSite.
     
  • Images. You can replace the default set of images within your SuperSite/PartnerSite Theme. This is especially useful when you have translated your SuperSite/PartnerSite content and would want to display images with embedded text in that language.
     
  • Javascript. The style of the Javascript Menu within your SuperSite/PartnerSite Theme can be equally easily modified, to suit your customized SuperSite/PartnerSite.

By applying a Theme you can immediately apply a predetermined set of design elements to your SuperSite/PartnerSite content. When you choose one theme to be the default theme for your website, the theme is applied to all existing pages and to new pages that you add later. 

How to Add/Modify a Theme or How do I edit the CSS, Images, Javascript of my SuperSite/PartnerSite?

IMPORTANT  

      

  1. To modify the CSS, Images and Javascript of your SuperSite/PartnerSite, you need to first add a NEW Theme.
     
  2. While adding a Theme, you need to select the Default Theme from where you want the default CSS, Images and Javascript to be initially loaded. As you modify these elements, your changes become a part of your new Theme.

    3.  

Adding a Theme

You can create your own Themes using the default Theme as mentioned below -

      

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
    IMPORTANT 

    The Default SuperSite/PartnerSite Theme cannot be edited. If you wish to change the look and feel of your SuperSite/PartnerSite, you need to create your own Theme and modify the same.

  3. In order to create your own Theme, click on the Create Custom Theme link on the top right-hand corner of this page.
     
  4. Provide a unique name for your Theme and click Create My Theme. The Theme thus created will be listed under Your SuperSite/PartnerSite Theme(s) section.
     
  5. Click on the Browse link next to the Theme to view the contents of the Theme.
     
  6. Here you will find folders for CSS (Cascading Style Sheet) files, Images and JavaScript files.

    7.  

 

Modifying your Theme (editing your SuperSite/PartnerSite CSS, Images, Javascript)

 

You can modify the CSS files (Cascading Style Sheets) for different sections of SuperSite and PartnerSite, by following the process outlined below:

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Now click on Browse next to the CSS folder.
     
  5. This interface lists all the sections. Click on Browse, adjacent to the section for which you wish to modify the style sheets.
     
  6. The following page lists all the CSS files used in the section you have chosen. Click on Edit, adjacent to the CSS file you wish to modify.
     
  7. You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
     
  8. Click on the Save Changes button beneath after completing the modification.
     
IMPORTANT 

If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.

Virtually every image in SuperSite and PartnerSite is customizable – should you not find any to your liking, you can replace it with another at any time.
 

IMPORTANT 

     

  1. In order to modify an image file in SuperSite or PartnerSite, you need to note its name. To get the name of the image, simply right-click on the image in your browser, and select Properties. Here, you would find the address for the image. For example, http://<prefix>.SuperSite/PartnerSite.myorderbox.com/getImage.php?src=image-name.gif, orhttp://<prefix>.partnersite.myorderbox.com/getImage.php?src=image-name.gif

    where image-name.gif is the name that you require.
     

  2. Also, there are some image files which are a part of the CSS itself; you would not be able to retrieve the filenames in the above manner. To retrieve the names of such image files, you need to check the style sheets for the section containing the image in question, and retrieve the image file name from there. Click here to find instructions on how to edit your SuperSite/PartnerSite/PartnerSite CSS files >>
     
  3. : You can follow the process mentioned below to replace the default header logo with the logo of your company. To do so, you need to replace the image named yourbrand.gif.

    4.  

 


Follow the process outlined below to modify any Image files in your SuperSite/PartnerSite:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Click on Browse link next to the Images folder.
     
  5. This interface lists all the images used by the SuperSite/PartnerSite.
     
  6. In the list, look for the name of the image you wish to modify. Click on Edit, adjacent to it.
     
  7. Click on Browse, and select the image you wish to upload in place of the default.
     
  8. Click on Upload Image. This will replace the default Image with the one you have provided, such that every page where the old image file was being displayed, would now display your uploaded image file.

    9.  

 

In addition to the default images, you can add/edit your own images as mentioned below:

      

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Click on Browse link next to the Images folder.
     
  5. Click on Browse next to the MyUploadedImages folder.

    6.  

 

Adding your own Images

     

  1. Click on the Add your own Images button on the top right-hand corner of this page.
     
  2. Click on Browse, and choose the image that you want to upload.
     
  3. Once the image is selected, click on Upload button.

    4.  

Editing Images added by you

     

  1. Click on the Edit link next to the image you wish to modify.
     
  2. Click on Browse, and choose the image that you want to upload.
     
  3. Once the image is selected, click on Upload Image button.

    4.  

After uploading an image using the above tool, you would need to link it from some HTML page on your SuperSite/PartnerSite.

IMPORTANT 

     

  1. If you have translated your SuperSite/PartnerSite content to multiple languages, then you may want to have images with text embedded on them in that particular language itself. To accomplish this you would need to associate different languages to separate Themes and within each Theme have Images related to only that language.
     
  2. If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.

    3.  

The manner in which the menu is displayed, can be modified just as easily:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
     
  3. Click on Browse besides the Theme which you need to modify.
     
  4. Click on Browse next to the JS folder.
     
  5. Click on Edit, adjacent to the menu_style.js file.
     
  6. You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
     
  7. Click on the Save Changes button beneath after completing the modification.

    8.  

     

IMPORTANT 


 How do I apply a Theme to my SuperSite/PartnerSite? 

You can display your SuperSite/PartnerSite in either the Default Theme provided by Gossimer or use any one of the Themes you have recently added. Follow the below mentioned process to accomplish this:

     

  1. Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
     
  2. In the Admin Area, click on the Configure Languages and Themes link.
     
  3. Here you may either set your Theme for the Default English Language or any other language added by you, by selecting the Theme from the Associated Themes drop-down.
     
  4. Click on the Save button to associate the selected Theme to a particular language.

    5.  

 

IMPORTANT 

The Theme you have selected will be applied to your SuperSite/PartnerSite ONLY after you have enabled that particular language.


 Click here to know how to configure Multiple Language support to your SuperSite/PartnerSite >>

Tags: , , , , , , , , , , , , , , , , , , ,

Filed in How do I customize the Content, Theme (CSS, Images, Javascript), HTML Structure of the SuperSite and PartnerSite? with 0 Comments
« Previous Posts
sidebartop

Recent Posts

sidebarbottom
sidebartop

Some good Links

sidebarbottom
sidebartop

Favorite Gossimer Links

sidebarbottom
sidebartop

Categories

sidebarbottom
sidebartop

Tags

Admin Control Panel Amp Api Biz Contact Details Control Control Panel Customer Control Panel Database Manager Database Name Details View DNS Domain Name Domain Names Email Address European Union Gossimer Gt 2 HTML http Invoice Linux Lt Management Interface Manage Web Hosting Service Microsoft Windows Parameters Payment Gateway Php Power Tool Registrar Reseller Control Panel Resellers Search Domain Servers Service Button Supersite View 3 Web Hosting Web Hosting package Web Hosting Service Web Server Web Service Website Builder Website Management
sidebarbottom
sidebartop

RSS Gossimer in the News

sidebarbottom
sidebartop

RSS Gossimer Promotions and Announcements

  • TechSupport Notifications February 28, 2010
    Technical support information and notifications […]
  • PHP4 Discontinuation - 18th September September 7, 2009
    As announced earlier, PHP4 will not be supported on our Linux Hosting Servers from the 18th of September, 2009. Please pass on this information to your Customers and Resellers to ensure that they can update their websites to work with PHP5. […]
  • .CN Launch - Coming Soon August 16, 2009
    We are glad to announce the launch of .CN - the most popular and fastest growing ccTLD worldwide. The .CN domain extension has seen an exemplary growth since its launch throughout the world. Earlier this year, .CN crossed over 13 million registrations to become the second most registered domain extension after .COM. Moreover, with China now representing the […]
  • Live Chat Product Discontinuation - Moved to 18th August August 16, 2009
    Based on feedback that we received from several Resellers, we have decided to postpone the Live Chat discontinuation to the August of 18th, 2009 at 12:30 UTC. From the 18th of August, it will not be possible to purchase new Live Chat packages but exisiting packages will continue to function normally. […]
sidebarbottom
© Web Hosting and Domain registration Knowledgebase