admin_tool1Add my vote for this tag installation7Add my vote for this tag security3Add my vote for this tag upgrade2Add my vote for this tag create new tag
, view all tags
Get Involved!
TWiki is an open source project with 10+ years of history, built by a team of volunteers from around the world, and used by millions of people in over 100 countries. The community is focusing on building the best collaboration platform for the workplace. We invite you to get involved!

ALERT! NOTE: This is a SupplementalDocument topic which is not included with the official TWiki distribution. Please help maintain high quality documentation by fixing any errors or incomplete content. Put questions and suggestions concerning the documentation of this topic in the comments section below! Use the Support web for problems you are having using TWiki.

Auto-generated twiki.conf to be included from httpd.conf

NOTE: Some people, including many using web hosts, do not have access to the Apache configure directories. If this applies to you, do not use the generator on this page - edit the various .htaccess template files included in the download. (They have instructions in them - their file names are all different, but include "htaccess.txt" in them.)

Note that TWiki does not work with directory names containing spaces (especially important to notice for Windows users). So choose an installation directory without spaces.

Configure your TWiki
Full file path to your twiki root directory (mandatory):
Empty transparent 16x16 spacer
URL path of the TWiki bin directory containing the scripts (mandatory):
Empty transparent 16x16 spacer
Empty transparent 16x16 spacer Example: /do for URL http://example.com/do/view/Main/WebHome
URL path of the TWiki pub directory containing file attachments (mandatory):
Empty transparent 16x16 spacer
Empty transparent 16x16 spacer Example: /pub for URL http://example.com/pub/Main/WebHome/File.txt
Choose your Login Manager:
Empty transparent 16x16 spacer None - No login
Empty transparent 16x16 spacer TemplateLogin - Redirect to the login template, which asks for a username and password in a form
Empty transparent 16x16 spacer ApacheLogin - Apache is configured to ask for authorization information
Prevent execution of attached files as PHP scripts if PHP is installed:
Empty transparent 16x16 spacer PHP4/5 Installed
Empty transparent 16x16 spacer PHP3 Installed
Empty transparent 16x16 spacer No PHP Installed
Block known rogue spiders (recommended on public TWiki sites):
Empty transparent 16x16 spacer Block rogue spiders, but exclude good ones like Google and Bing
Block direct access to viewing attachments that ends with .htm or .html (recommended against spam abuse):
Empty transparent 16x16 spacer Block .htm and .html
Block direct access to viewing attachments in Trash web (recommended against spam abuse):
Empty transparent 16x16 spacer Block Trash web
Secure file attachments:
Empty transparent 16x16 spacer No: Apache delivers the files directly. Attachments are not protected with the access control setting of its page, e.g. anyone who knows the direct URL of the attachment can access it, regardless of the TWiki access control setting.
Empty transparent 16x16 spacer Yes: The attachments are delivered with the viewfile script, which honors the access control setting of the page where the file is attached to. Accessing files this way is more secure, but can be much slower. The TWiki web and Sandbox web are excluded for performance reasons. The viewfile sets the mime type based upon file name suffix. Unknown types are served as text/plain which can result in corrupt files.
Page to return to when authentication fails:
Empty transparent 16x16 spacer TWikiRegistration
Empty transparent 16x16 spacer ResetPassword
Empty transparent 16x16 spacer None. Use Apache default 401 message
Execution of TWiki's Perl scripts:
Empty transparent 16x16 spacer mod_cgi: CGI (Common Gateway Interface) (detail)
Empty transparent 16x16 spacer mod_cgid: CGI using an external CGI daemon (detail)
Empty transparent 16x16 spacer mod_perl: Perl interpreter embedded into the Apache server (not recommended unless you have thousands of users) (detail)
Apache version installed:
Empty transparent 16x16 spacer Apache 2.4 or newer
Empty transparent 16x16 spacer

twiki.conf created based on your configuration

The text field below now contains a complete twiki.conf file to be included from httpd.conf. In many distributions the twiki.conf file is automatically included by placing it in the directory that contains the other included Apache config files, typically in /etc/httpd/conf.d or /etc/apache2/conf.d. (Not recommended, but it can also be placed anywhere else if you add the following line to the end of your main httpd.conf file: include "/path/to/twiki.conf".)

  Press this button to select all the text in the textarea. Then copy the text to the clipboard and paste it into the twiki.conf file.

mod_perl startup script

If you choose to run mod_perl you can create a file /var/www/twiki/tools/mod_perl_startup.pl and copy all the text from the text area below and paste into this file.

ALERT! This file is written for mod_perl2, under Apache 2 and later. For mod_perl under Apache 1.3, you will have to, at least, change the ModPerl::RegistryLoader into Apache::RegistryLoader, and change the PerlResponseHandler in the configuration above to PerlHandler.

ALERT! Before you enable mod_perl in your webserver, you have to configure TWiki. Otherwise, you'll face a chicken-and-egg problem, and would get something like this in your Apache error logs:

[error] Content-type: text/plain\n\nPerl error when reading LocalSite.cfg: \nPlease inform the site admin.\nBEGIN failed--

Contributors: KennethLavrsen, JoshuaCharlesCampbell, PeterThoeny, MatthewTaft

Comments & Questions about this Supplemental Document Topic

Thank you very much Kenneth for sharing this with the TWikiCommunity!

-- PeterThoeny - 03 Jul 2006

I'm not sure if I need this or not. Frankly, it confuses me a bit. Here's my comments. 1) The first field asks for the full path... I think (but am not sure) it means the file path, not the URL path. This is a common issue with most TWiki docs. 2) Are all fields required to create a valid file? For example, do I have to lock this down to specific IP addresses? What if I leave it blank? 3) Do I need mod perl? I dunno... 4) This sentence is confusing: "The text field below now contains a complete twiki.conf file to be included from httpd.conf" Does that mean that I should take the text from the text box and paste it inside of my httpd.conf file?

For now I am just going to steer clear. Thx anyway!

-- GeoffreyMack - 06 Oct 2006


  • On 1). Yes this is the file path. Not the URL path. I hoped the default example path /var/www/twiki would tell you that since this is a common path on a Linux machine for the Apache folders.
  • On 2). You must give a path name to the twiki root folder. Like /var/www/twiki. You do not need to give a list of IP addresses or names. It is recommended to protect your configure. If you read the INSTALL.html in the twiki root you get the right context.
  • On 3) No you do not need mod_perl. mod_perl needs to be installed on your Apache installation for you to be able to use it and you need a lot of RAM. mod_perl compiles all the perl code ONCE and keep it in RAM. This speeds up the execution of TWiki by at least factor 2. But mod_perl also keeps all variables in RAM so the programs must be written with great care. The TWiki core and the default plugins are pretty mod_perl safe now. But some other plugins do not work with mod_perl. I recommend to start a new TWiki installation without. And once it works you can try and activate it. Read the topic ModPerlUnix for more information. This ApacheConfigGenerator is a helper that generates a working apache config also for mod_perl but you need to know more about it to use it. As a beginner, run without.
  • On 4) I do not recommend editing the default httpd.conf file. Normally distributions have an include statement in httpd.conf that includes all files that ends with .conf in a specific directory often called something like /etc/httpd/conf.d. You simply create a file called twiki.conf in this directory and paste in all the text from the text area. And then restart Apache. The topic TWikiOnRedHat has a very detailed step by step guide how to install TWiki including how to setup the config files for Apache using this topic.
-- KennethLavrsen - 11 Oct 2006

When I use the settings generated by your tool with my Apache/Mod_PERL installation, the WysiwygPlugin gets disabled. Is this a known bug?

-- AlokNarula - 23 Nov 2006

The script should quote the value for AuthUserFile. I as installing Twiki under Windows and it was using c:\program files\...\twiki\... and therefore the value for AuthUserFile had a space, which was not quoted by the generator in this page. This caused Apache2 to fail to start. If spaces are not supported, this script should warn the user. If, on the other hand, paes are supported, then the script should quote the value. Note how it quotes pretty much every other value. It took my a while to isolate the problem and figure out why apache2 would no longer start.

-- MarcioMarchini - 15 Jan 2007

The previous user was probably adding notes using the WYSIWYG editor, which totally messed up the form fields (not user error, is one of the many WYSIWYG editor bugs). I restored the previous topic version and merged the changes in.

-- PeterThoeny - 30 Jan 2007

I added new many more spiders to the blockAccess list; this is from twiki.org's Apache configuration.

-- PeterThoeny - 06 Feb 2007

Thks, I was starting to think to add mod_perl to my apache server, but knew nothing, reading this it'was 10min to get the twiki running twice fast than before.

-- MarcoSilva - 04 Mar 2007

Peter, it should be nice if we could rank these tips and howtos, like in vim.org, that has simple three buttons to rank its tips. Anyway, always in gratitude with you for twiki.

-- MarcoSilva - 04 Mar 2007

The tags have a vote function. Please add your vote to existing tags or add additional tags to topics you find useful. Topics with the highest tag votes show up first in the tag search page.

-- PeterThoeny - 05 Mar 2007

With all the "BrowserMatchNoCase" lines, the generated document no longer fits into a text box without scrolling. Would it be possible to save the plain text for the generated twiki.conf to another page, which we can click on and download?

-- KeithLofstrom - 21 Mar 2007

I think for security we should avoid exposing the TWiki root as an htdoc enabled directory. Sure, it can be secured as done by explicitely denying access to sub directories, but what if an admin creates a new sub directory and does not realize it is exposed?

So, this setup is more safe:

ScriptAlias /twiki/bin "/var/www/twiki/bin"
Alias /twiki/pub "/var/www/twiki/pub"

These are the only two directories that need to be exposed.

-- PeterThoeny - 27 Aug 2007

Only problem with this is that then the root html files are not accessible. But my guess is that not many have them there anyway.

-- KennethLavrsen - 03 Sep 2007

I think for security we better not have the twiki root exposed as htdoc root. An admin has file access during installation, thus can point a browser to the file URL to see INSTALL.html. Also, the http URL is not accessible before Apache config is done, so TWiki root exposure is a moot point.

-- PeterThoeny - 04 Sep 2007

added expires_module section - whatever time limit you set, will be how long the browser will wait until it tests to see if the static files have changed - thus reducing your round trip times dramatically, and reducing the number of connections needed to your server.

-- SvenDowideit - 27 Sep 2007

It would be nice to enhance this generator for an extranet setup where the whole twiki/bin and twki/pub directories are under authentication.

Example for twiki/bin:

AuthUserFile /path/to/twiki/data/.htpasswd
AuthName 'Enter your WikiName'
AuthType Basic
ErrorDocument 401 /error.html
Options -Indexes
<FilesMatch "configure.*">
  require user PeterThoeny
<FilesMatch ".*">
    require valid-user

Example for twiki/pub:

AuthUserFile /path/to/twiki/data/.htpasswd
AuthName 'Enter your WikiName'
AuthType Basic
ErrorDocument 401 /error.html
<FilesMatch ".*">
  require valid-user

-- PeterThoeny - 02 Jan 2008

"AddType text/plain .shtml .php .php3 .phtml .phtm .pl .py .cgi"

Be aware that this directive introduces an issue if for example you have the associated html page for the wysiwyg editor. as the text/html document will have text/plain mime type. Maybe wise to limit the coverage of the directory or location.

-- AlexandreDulaunoy - 11 Feb 2008

I really don't think that the W3 rules should be there; they prevent using the W3Cs validator. PatternSkin goes to a lot of trouble to validate, and people should be proud of that.

-- ChrisFLewis - 13 Feb 2008

I can't start apache on my Mac when the line php_admin_flag engine off is in the config file.

-- ArthurClemens - 19 Feb 2008

If you're using mod_perl, the documentation should read that you must have that Perl script in place, otherwise Apache won't start properly.

-- JimRizzo - 22 May 2008

It's really important to use the right handlers - in reality, to use RegistryPrefork. I spent a couple of maddening days chasing my tail trying to get mod_ssl, mod_rewrite, mod_perl and twiki's template login system playing happily together. I kept getting periodic episodes in which you would have to pass through the login template multiple times.

Once I've had some sleep and gotten through finals, I'll (at the least) get the fully documented setup out there for folks to peruse. Don't know that I'll deal with adding it to the generator though...

-- HilaryHolz - 04 Jun 2008

Thank you Hilary for the feedback. Looking forward seeing details on how to improve docs.

-- PeterThoeny - 04 Jun 2008

Small correction: the regexp for blocking direct access to attachments that end with .htm or .html was missing an [lL]

-- MarkusUeberall - 15 Jul 2008

The generated mod_perl startup script contained the twiki base path. my $binbase = '/var/www/html/twiki/bin'; # must be set by the user This path was apparently not substituted to the path entered in the form. This causes weird errors when using mod_perl. See ModPerlWierdness.

So I corrected this topic accordingly. Hope that was right.

-- LarsKanis - 18 Jul 2008

Added a warning message for mod_perl: You should first configure TWiki before trying to enable it, otherwise Apache won't start (no LocalSite.cfg)

-- OlivierRaginel - 15 Aug 2008

Merged mod_perl settings in the configuration so it can be enabled / disabled using things like a2enmod perl / a2dismod perl.

Added a warning for Apache 1.3, and moved the warning that mod_perl should be enabled AFTER configuring TWiki below the mod_perl_startup.pl, as a user suggested.

Removed the mod_perl option, and merged it directly in the configuration using Apache IfModule directives. This eases the deployment of twiki, as one needs first to set it up without mod_perl to run configure, and then to enable mod_perl if wanted for speed. Problem is that if someone has mod_perl installed, and tries to install TWiki, the mod_perl_startup.pl has to exist.

-- OlivierRaginel - 13 Oct 2008

Olivier - I discovered (when I tried to do exactly that in the debian package) that it doesn't always work - resulting in an apache that doesn't start frown

-- SvenDowideit - 13 Oct 2008

Should the \ be there? It caused a problem on my end of not using any of these.

   <FilesMatch \"(attach|edit|manage|rename|save|upload|view|rest|.*auth).*\">

I think this should be;

   <FilesMatch "(attach|edit|manage|rename|save|upload|view|rest|.*auth).*">

-- PhilipBloom - 22 Oct 2008

Oliver - I had to comment out the two sections on mod_perl to get apache to start. This is on Red Hat.

-- JimCrum - 11 Nov 2008

The error in the apache log was that it couldn't locate .../twiki/tools/mod_perl_startup.pl in @INC

-- JimCrum - 11 Nov 2008

That error should go away if you set the proper path in PerlRequire /var/www/twiki/tools/mod_perl_startup.pl. FYI, I tried to run twiki.org under mod_perl but for whatever reason it was not stable enough under high load, so I turned it off.

-- PeterThoeny - 11 Nov 2008

The auth option says "ApacheLogin - Apache is configured to ask for authorization information", but the config generated by the current generator does not ask for authorization on attachments (/pub). This is very misleading, since the option implies that apache is configured to ask for authorization on any request. Either protect all directories with authentication or explicitly mention directories that are not protected. Thanks

-- NicholasSushkin - 2009-09-25

It is already described the TWikiAccessControl how to protect attachments.

Agreed, the limitation of the default config of not protecting attachments could be pointed out also in the generated Apache config file. TWiki is an open source project, please feel free to enhance the Apache config generator.

-- PeterThoeny - 2009-09-28

I changed the Apache config file to not expose the twiki root as an htdoc enabled directory. This is done to reduce the risk of making mistakes in the Apache config file, such as forgetting to secure a new directory added below the twiki root. More at DontExposeTWikiRootAsHtmlDocRoot.

-- PeterThoeny - 2009-10-26

I added an option to secure file attachments. Also updated TWikiAccessControl#SecuringAttachments.

-- PeterThoeny - 2009-11-06

Do I need an .htpasswd file ? When I select 'NoLogin' the code in the config file file still contains The Password file for Twiki Users, I'd rather use a login based on my LDAp groups. What shouel I do ?

-- MarcDurbach - 2009-12-02

Hi - as soon as I Include twiki.conf in my httpd.conf file, my Apache won't start. Does anyone have any ideas? Running on Windows 2008 R2 server.

-- RussMartin - 2010-04-28

This section is about the documentation of the generator page. Please ask support questions in the Support forum.

-- PeterThoeny - 2010-04-28

Hi , When ever i configure twiki with mod_perl_startup.pl script it always show the error message can't read /erpp1/twiki/mod_perl_startup.pl during restarting server...After disable this mod_perl_startup.pl script in twiki.conf the server started properly.. But find a problem that 403 error :you doesn't have autherisation to view the file /twiki/bin/configure ... How can i solve

-- GopiKrishna - 2010-07-13

This section is about the documentation of the generator page. Please ask support questions in the Support forum.

-- PeterThoeny - 2010-07-13

To-do: We need to update the Apache config generator with a checkbox to enable/disable mod_perl. See support question Support.SID-00964

-- PeterThoeny - 2010-09-09

Updated. The twiki.conf file now only writes the directives enabling mod_perl when the check box "Enable mod_perl" is activated. A further revision could be made below the mod_perl startup script section; that information only applies when "Enable mod_perl" has been checked.

-- MatthewTaft - 2010-09-09

Thank you Matthew! Please feel free to make the mod_perl startup script section conditional as well. That can be done by enclosing the whole section in a div with style="visibility:visible" or style="visibility:hidden".

-- PeterThoeny - 2010-09-10

Updated. Had an interesting time getting that to work in the editor, and ended up wrapping the opening and closing div in WYSIWYG_PROTECTED spans. Also added display:none; so the white space would go away when that section is not displayed.

-- MatthewTaft - 2010-09-10

Having trouble updating this, actually. Right now, it works, but it won't work the next time someone edits this page. Basically, right above the section starting with "mod_perl startup script" I placed this code:

<p><span class="WYSIWYG_PROTECTED"><div%IF{"defined enablemodperl" then=">" else=" style=\"display:none;visibility:hidden;\">"}%</span></p>

This part stays there. When mod_perl is enabled, this div is hidden. However, I need to close off the div below the whole section. Right above the "Contributors" section, I place this:

<p><span class="WYSIWYG_PROTECTED"></div></span></p>

When I save the document, this keeps. However, when I click to "Edit" the document again, this part goes away so that there is no closing div. This means the rest of the document, including all the comments, gets hidden by default because mod_perl isn't selected by default. Having a hard time working from within this WYSIWYG editor. Anyone with more experience here is begged to fix this smile

-- MatthewTaft - 2010-09-10

Thanks Matthew, very much appreciated! I added your name to the contributor section.

I disabled the WYSIWYG editor for this page with a Set TINYMCEPLUGIN_DISABLE = on setting. FYI, you can tell the WYSIWYG editor to leave a section of text alone by enclosing it in <sticky> ... </sticky> tags.

-- PeterThoeny - 2010-09-10

I'm trying to deploy TWiki 5.0.1 with Apache configuration generated here. If I use "cgi-script" the "bin/configure" script is shown in plain text.

If I use "perl-script" I can run "configure" script but I lose (perl) variables on the way. The message error is "Variable "$localLibFailure" will not stay shared at..."

What can I do? I tried to disabled mod_perl for "bin" directory, for whole documentroot.. I do not know what else to do. I do not understand where I should use and where I should't use mod_perl. Canyou help me? Thank you.

-- RobertoOFC - 2011-04-26

This section is about the documentation of the generator page. Please ask support questions in the Support forum.

-- PeterThoeny - 2011-04-26

I added "URL path" and removed the password of the configure script (no longer needed on Apache level because configure script now has its own password handling).

-- PeterThoeny - 2012-03-30

I notice that, although there's a text box prompting me for "IP address range or hostnames that will have access to configure", I don't see where "<FilesMatch "^(configure)$">" section with "Allow from (list of space separated IPs)" is being added to the conf file. Is this a possible bug? (or maybe I'm missing something)?

-- TroyChard - 2012-05-11

Oops, that form field is obsolete. Now removed.

-- PeterThoeny - 2012-05-11

I added support for Apache 2.4, and I made the block spiders part optional.

-- PeterThoeny - 2012-05-12


the first step, "Enter the URL path of the TWiki bin directory (mandatory):"

What if my url path begins with ~username? Do I add this also?


Hi Peter!

-- JasonBrooks - 2012-06-14

Yes you do, such as /~jason/twiki/bin

Long time no see, Jason, welcome back!

-- PeterThoeny - 2012-06-15

Please help me! I am new to TWiki and I am trying my hardest to install TWiki and configure Apache files on Mountain Lion. This will be easy for you guys but is someone willing to hold my hand and take me through this set up for a college assignment I have coming up? Please reply!

-- SallyGale - 2013-01-06

Sally, please see TWikiOnMacOSXSnowLeopard and ask support questions in the Support forum.

-- PeterThoeny - 2013-01-07

Hi, I have installed succefully apache and twiki. when i hit the URL: http://localhost/twiki/bin/configure its showing 404 error...could you please suggest me...is there any additional configuration in apache?

-- Manivannan L - 2013-05-29

Please use the Support forum if you have questions about TWiki installation. This comment section is about the documentation of this topic.

-- Peter Thoeny - 2013-05-30

The Twiki installation guide, http://twiki.org/cgi-bin/view/TWiki05x01/TWikiInstallationGuide, says in step 8 (Protect the configure script): "The TWiki:TWiki.ApacheConfigGenerator lets you setup who has access to the configure script." And indeed an earlier comment here speaks of a text box where one can enter an "IP address range or hostnames that will have access to configure". But I don't see these options. Have they been removed? It seems that there's a discrepancy between this page and step 8 of the installation guide, though whether documentation or functionality I can't tell.

-- Larry Denenberg - 2013-07-01

Addendum to previous comment: Examination of the history suggests that the trouble is not on this page, but on the installation guide. Possibly step 8 there is now obsolete if configure itself is doing all the work.

-- Larry Denenberg - 2013-07-01

Thank you Larry for pointing out the issue with "protecting the configure script by IP address". You are correct with your assessment, this is obsolete now because the configure script is protected by password. I updated the TWikiInstallationGuide accordingly.

-- Peter Thoeny - 2013-07-01

The TWiki-6.0.0.zip file after unzipped in the document root directory... and the Welcome to TWiki page comes up... displays "TWiki-5.0 Release Notes" instead of 6.0... and the "Configure TWiki" link opens up the script as a text file instead of running it to configure TWiki. The second is probably a boneheaded mistake on my part but the first is a problem with a file in the download zip file.

-- Jeffrey Lovretich - 2013-11-07

Thanks Jeffrey for the feedback. For better security, TWiki should not be put into the HTML doc root. I'll update the outdated index.html with a warning not to do so. In future best to file a bug report at TWikibug:WebHome.

-- Peter Thoeny - 2013-11-07

I cleaned up index.html in the twiki root, explained and tracked in TWikibug:Item7378.

-- Peter Thoeny - 2013-11-09

I updated the mod_perl startup script based on TWikibug:Item7440 report. Thanks TerjeAndersen!

-- Peter Thoeny - 2014-02-24

Hi peter, thanks for your greatest job! Why I can find LocalSite.cfg file. After I disable login, I got the following reponse from browser

Perl error when reading LocalSite.cfg: Please inform the site admin. BEGIN failed--compilation aborted at /Library/WebServer/Documents/twiki/lib/TWiki.pm line 575. Compilation failed in require at /Library/WebServer/Documents/twiki/bin/view line 41. BEGIN failed--compilation aborted at /Library/WebServer/Documents/twiki/bin/view line 41.

-- andy mao - 2014-04-10

Andy, please ask support questions in the Support web.

-- Peter Thoeny - 2014-04-10

A minor remark on mod_perl usage: In the current config, the configure script is excluded from being processed with SetHandler perl-script, so it will be processed with "traditional" CGI. This means that the hint to activate mod_cgi would be helpful in any case. On the other hand, if it is intended to process configure with mod_perl but exclude it from precompilation in the mod_perl startup script, then the FilesMatch directive should be adapted accordingly. I don't know what's better and don't know whether I come round to test both methods. Right now I stick with mod_cgi ...

-- Harald Jörg - 2014-06-14

Thanks Harald. Could you pick one you think is right and update the generator accordingly?

-- Peter Thoeny - 2014-06-14

Hello everyone. I tryed to generate mostly all combinations of this generator, but none resulted on a working environment, mostly the best results were a non completely rendered site, and the main page with a warning on configuration and permissions. I will use twiki as an intranet, and it will run on apache virtual hosts, on a server with already some web apps, mysql, apachd 2.2, php5 and so on. MOst of the errors when acessing the page on apache are:

[Wed Oct 15 22:39:53 2014] [error] [client] script not found or unable to stat: /var/www/twiki/bin/TWiki, referer: http://twiki.franca.unesp.br/do/view/Main/WebHome

and on configurations, iv changed the ScriptAlias from /do to /bin but still wont work, im posting my apache.conf with virtual hosts configuration, and a print of the pages warnings. Any help appreciated, it it is possible to run twiki with virtual hosts. Iv tryed on irc on freenode, but thers very few people, most of them dont talk much. big grin

warning: http://prntscr.com/4wldv9 site rendering: http://prntscr.com/4wle12 my apache conf: http://apaste.info/tey

-- Carlos Gomes - 2014-10-16

Carlos, please ask support questions in the Support forum, thank you.

-- Peter Thoeny - 2014-10-16

Please use the Support forum if you have questions about TWiki features. This comment section is about the documentation of this topic.
Edit | Attach | Watch | Print version | History: r99 < r98 < r97 < r96 < r95 | Backlinks | Raw View | More topic actions
Topic revision: r99 - 2014-10-16 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2015 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.