User Tools

Site Tools


te3:customizing_and_renaming

This is an old revision of the document!


Customizing and renaming

Settings / General settings / Customizing and renaming TE3 modules

Each site should be as unique as possible - if the same link scheme, cookie names and directory structure repeat over and over again on hundreds of different sites, this can have a negative impact on search engine rankings.

We have implemented several different options for customizing and renaming TE3 modules and we strongly encourage you to make TE3 on each of your sites more unique - it may take some effort but you'll be avoiding potential complications related to search engines.


TE3 uses up to four types of cookies - ''in.php'' module sets up a basic cookie and a bookmark cookie for each visitor of your site. If you are using “Pages” module, Te3 sets up a Pages cookie, and if your External feature is enabled, TE3 sets up an external feature cookie.

Cookie names are randomly generated at the installation stage. Although not necessary, we advise you to rename them manually - search engines will recognize actual words as more authentic than computer generated ones. If you manage several websites, be sure to create unique cookie names for each site.

Example - renaming cookie names


Thumb image directory name

There are two methods for customizing thumb image directory name:

1. Change the original thumb image directory name

Change the original thumb image directory name from “thumbs” to a name of your choice.

Example - renaming thumb image directory name

2. Place "thumbs" directory into the root html directory

Place “thumbs” directory into the root html directory of the domain (public html) using “dot dot slash” (../).

Example - placing "thumbs" directory into the root html directory


Toplist directory name

There are two methods for customizing toplist directory name:

1. Change the original toplist directory name

Change the original toplist directory name from “toplist” to a name of your choice.

Example - renaming toplist directory name

2. Place "toplist" directory into the root html directory

Place “toplist” directory into the root html directory of the domain (public html) using “dot dot slash” (../).

Example - placing "toplist" directory into the root html directory


''out.php''

There are two methods for customizing out.php:

1. Rename your ''out.php'' into ''anything.php'' (for new sites)

When you rename out.php in your Customizing and renaming menu, file name automatically gets renamed as well. This method could prove problematic if you have an existing site. When you rename out.php, all links on your site will immediately become broken. If your site is already getting traffic, we recommend the 2nd method instead.

Example - renaming ''out.php'':

2. Include ''out.php'' into another file (for new sites and for running sites)

The advantage of this method is that if your site is already getting some traffic, surfers won't experience broken links on your site while you are switching links from old to the new paths. In general this method might be better for both, existing (running) site and new site alike.

Example - including ''out.php'' into another file:


''out.php'' parameters

You can customize “standard” TE3 out.php parameters by appointing them names of your choice. You can choose more than one name for a single parameter (e.g. id: domain,d,name).

If you decide to reconfigure outgoing tracking, you'll have to modify all clickable links on your site. This could be problematic if your site is already getting some traffic. We advise you to retain the original out.php parameter name as one of the appointed parameter names in order to avoid potential problems (e.g. id: id,domain,d,name). This will prevent surfers from experiencing any broken links on your site while you are switching links from old to the new paths.

If you manage several websites, be sure to create unique out.php parameter names for each site.

Example - renaming ''out.php'' parameters

te3/customizing_and_renaming.1417162904.txt.gz · Last modified: 2014/11/28 08:21 by moderator

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki