Loading...
 
Skip to main content

History: Apache Clean URLs

Preview of version: 109

Clean URLs with Apache .htaccess

Tiki supports search-engine friendly web addresses (SEFURLs or clean URLs), which are short versions of Tiki URLs, thanks to Apache Rewrite Rules. Some search engine crawlers do not process links with trailing parameters, so transforming the syntax makes the URL more search-engine friendly. By configuring your server properly, Tiki can understand clean URLs so that such short URLs will bring up a Tiki page, and by configuring Tiki properly, Tiki will produce clean URLS and build them into menus, static links, etc. This page explains both steps: how to make Tiki understand and produce clean URLs. See also: htaccess

Examples

Here are some examples of how clean URLs work for various types of Tiki pages:

Notice how any text after https://tiki.org/article374-Tiki will work, such as https://tiki.org/article374-Tiki-Passes Thus, the article title can be modified and the URL still works. Canonical URLs are there to inform search engines of the correct one.

 Note
Note that both the short and long URLs will still access your site.

Steps to Activate Clean URLs

  1. Activating input rewrite rules on your server (so Tiki can understand clean URLs)
    • This allows accessing your site with clean URL's
  2. Enabling the SEFURL or SEFURL Filter (version 3.0) feature (or both) in Tiki (So Tiki will produce clean URLs)
    You can do so at "Admin home/Control Panels > Search engine friendly url (tiki-admin.php?page=sefurl) > Activate the feature: "Search engine friendly URL"
    • This causes internal Tiki links to be rewritten into clean URLs. The generation of the clean URLs is governed with 'output rewrite rules' that are in the code before Tiki version 3.0 and in the database beginning with 3.0.
  3. Uncomment SEF URL section of the robots.txt file (Optional) Tiki 16+
    • To do so, open the robots.txt located in the root directory of your tiki install, and remove the #'s in front of the SEF section.
    • This step will remove the basic URL's in search engine results in favour of the Clean URL's.

Step 1: Activate Input Rewrite Rules on Your Server

Web Hosting Service Using Apache

If you have Tiki version 1.9.x or greater and are using a web hosting service that uses Apache, then input rewrite rules can be activated as follows:

  • Rename the file named _htaccess in your Tiki root directory to .htaccess (or create a symbolic link to .htaccess).
    • This will automatically bring in suggested rewrite rules shown below (at Suggested Input Rewrite Rules ) into the .htaccess file. The _htaccess file is included as part of the Tiki download (since version 1.9.3) but is not activated by default because it may not work with all server configurations.

Apache Configuration When Managing Own Server

For better instructions on how to do this see Digital Ocean.

If you manage your server and are using Apache, be sure to

  1. Load the rewrite module. Something like this line in httpd.conf: LoadModule rewrite_module modules/mod_rewrite.so (adjust the path if necessary). You can check it is ok if you see the mod_rewrite in the apache loaded modules (apachectl -M command).

  2. Enable the access to .htaccess. To do so you must have lines like:

    Copy to clipboard
    <Directory "/"> ... Options FollowSymLinks AllowOverride FileInfo ... </Directory>

    Adapt the directory path to your need. This block can be in httpd.conf or in your virtual host config (vhosts.d directory in apache2).

    The documentation for Apache2 core says that the <FilesMatch> section requires:

    Copy to clipboard
    AllowOverride All

  3. Restart your server

Web Servers Other Than Apache

If you or your web hosting company is using a web server other than Apache (IIS for example), see your server manual or contact your web hosting service to find out how to activate rewrite rules on your server.

Suggested Input Rewrite Rules

Below are the rewrite rules for different versions of Tiki that pull into the .htaccess file automatically when the steps above for Apache web servers are followed.

6.x version
[+]

Step 2: Configure Tiki to Produce Clean URLs

Now that your input rewrite rules have been set, you now need to configure Tiki to activate the output rewrite rules so that Tiki will generate SEFURLs internally in menus, static links and elsewhere.


Starting with version 3.0, there is a search engine friendly feature icon directly on the Admin Home page that will look something like this:
Image
Clicking on that icon will bring up the search-engine friendly url admin page (although you could reach this page through the paths described above for previous versions as well):
Image
Search engine friendly url
Selecting the first checkbox will activate the SEFURL feature within Tiki, meaning that some links used in and elsewhere in Tiki will be search-engine friendly. This doesn't work for all links because not all of the templates have been updated, that's why there is a second checkbox...

Search engine friendly url Postfilter
To generate SEFURLs for all Tiki links, also check the second checkbox which creates short URLs by filtering the output. The SEFURL Postfilter consumes more processor (CPU) time than the non-filter version (it deals with all the text and it deals also with cached text like modules while the 'on the fly' filter does not do it. In future versions the SEFURL Postfilter will not be used - it is only necessary until the template SEFURL work is finished. Either one or both features (SEFURL and SEFURL Postfilter) may be used.

List of Url Parameters that should go in the path
This is used if you want a post or get variable to be represented in the sefurl. For instance if you have a url like tw.org/tiki-index.php?page=xxx&lang=en and if you put lang in the setting, the sefurl will be tw.org/en/xxx. You can generalize to any number of parameters. For a setting lang,locale, an url tw.org/tiki-index.php?page=xxx&lang=en&locale=us, the sefurl will be tw.org/en/us/xxx. This setting requires you adapt your .htaccess.

Display article title in the sefurl
Clicking this checkbox will add the title of the article to the url for a link to that article. For instance, tiki-read_article.php?articleId=1 will be transformed into article1-My-article-title. This does not work with the postfilter, only with 'on the fly filter'.

Display blog title in the sefurl
Similar to the article checkbox, clicking this checkbox will add the title of the blog to the url for a link to that blog. This does not work with the postfilter, only with 'on the fly filter'.


Within Tiki,

  1. Go to Admin Home -> Features -> Experimental -> Search engine friendly url (checkbox)
    + Or use the following URL to get to the Features page (since version 2.0): your URL/tiki-admin.php?page=features
  2. Check the box for "Search engine friendly url" to select this feature
  3. Click "Apply" to activate the feature
    Here's a screenshot:

    Image

Step 3: Configure Tiki to Show Clean URLs in Search Engine Results


As of Tiki16 or greater, you may optionally remove the basic urls from search engine results. This will cause your Clean URL's to show by default in any search engine that uses a robots.txt file (including Google).

When Clean URL's are enabled, it creates a second set of Clean URL's. The original URL's still exist, and by default, search engines will crawl and index them. Removing "duplicate content" is considered to be a good SEO practise and failing to do so generally results in a mild ranking penalty.

To enable this option, open the robots.txt file in your Tiki root directory and uncomment the SEF section by removing the #'s that start new lines. Uncommenting these lines without first completing steps 1 & 2 will prevent your website from being crawled or indexed.

Changing Rewrite Rules

You can customize the rewrite rules but it is important to note that that the input and output rewrite rules are connected, so that if you change one you may need to change the other.

  • You can add as many input rewrite rules you want. For instance if you want to be able to access a forum with forum1 or forum_1, no problem. Add the adequate rule in the htaccess that will rewrite forum_1 to tiki-view_forum.php?forumId=1
  • But if you want to change the output "rewrite" rules in Tiki, you must adapt the input rewrite rules
  • Starting with Tiki version 3.0, the output rewrite rules are in the table tiki_sefurl_regex_out

Developer's Corner

The 'on the fly' filter can use 2 smarty tools: prefilter and a function. Here's an example:

Copy to clipboard
<img src="{$fileId|sefurl:thumbnail}" /> <a href="{sefurl page=$next_info.pageName structure=$home_info.pageName page_ref_id=$next_info.page_ref_id}"> <a href="{$listpages[ix].articleId|sefurl:article:with_next} show_comzone=y#comments">


Both filters use tiki-sefurl.php to rewrite the urls.

Alias

Short URL | Short URLs | ShortURL | ShortURLs | ModRewrite | Mod_Rewrite | Friendly URL | Friendly URLs | Clean URL | Rewrite Rules | Rewrite Rule | Clean URLs

History

Advanced
Information Version
Marc Laporte This is already a header. No need to add bold 112
Marc Laporte 111
Marc Laporte 110
Marc Laporte 109
Marc Laporte 108
Marc Laporte Fix breakage from merge of info.tiki.org 107
Marc Laporte Outdated 106
drsassafras removing duplicate alias 105
Yves Kipondo 104
James Geddes add link to digital ocean 103
Roberto Kirschbaum 102
Roberto Kirschbaum 101
Roberto Kirschbaum Added apachectl -M as a means of checking if mod_rewrite is loaded 100
drsassafras 99
drsassafras Added robots.txt basic instructions, clean up text a bit, removed 2 broken images, removed 1 broken iframe. 98
Xavier de Pedro 97
Xavier de Pedro 96
Marc Laporte 95
Marc Laporte 94
Marc Laporte Using actually working links 93
Marc Laporte 92
Marc Laporte 91
Marc Laporte Fix incorrect example and add some info about Canonical 90
Torsten Fabricius change page name to "Apache Clean URLs", added old name as (alias(Clean URLs)) and changed first headline due to adding lighttpd to the wikistructure 89
Marc Laporte 88
Leu Added new page htaccess so remove alias 87
Marc Laporte 86
lindon 85
lindon 84
lindon 83
lindon 82
lindon 81
lindon 80
lindon 79
lindon 78
lindon 77
Xavier de Pedro 76
Xavier de Pedro 75
Xavier de Pedro 74
Marc Laporte shorter links 73
KMull Added warning for MediaTemple (gs) Grid-Service users 72
Marc Laporte 71
sylvie 70
sylvie 69
Marc Laporte 68
Marc Laporte 67
Marc Laporte shorter page 66
Marc Laporte 65
Marc Laporte 64
Marc Laporte 63