With many CMS and blog packages, a MySQL database (at €12 per year excl. VAT) is often required. You can request this via the communication module at MyVEVIDA.
Please see the documentation on the relevant CMS system for more information.

Installing a CMS such as Mambo, Joomla, Etomite (or blogs like Pivot, WordPress, webshops like osCommerce and Zen Cart, galleries like Coppermine, Gallery 2.0, etc.) and the like often requires the ability to write to a configuration file. By default IUSERs (visitors) have no write permissions, so online installation attempts via the web server will return an error message.


For optimal installation:
Use MyVEVIDA to delete the permissions from the folder where the CMS/blog should be installed (wwwcms, wwwblog or wwwshop, for instance). To do so, you must log in with your FTP login details, which will give you adequate permissions to write to all necessary configuration files. The setup will also be protected from undesired users.
If this folder is wwwcms for instance, then delete the permissions from wwwcms. After installation, your CMS/blog will be accessible at http://www.example.com/cms/.

If you want the CMS/blog installation to be accessible at http://www.example.com, then delete the permissions from the www folder (you cannot use a ‘trailing slash’ in MyVEVIDA, so delete the at the end of www).

After successful installation, you can use MyVEVIDA to standardize permissions (for the folder whose permissions you deleted) so the website can be accessed normally again. After this, you can assign write permission to the folders that need them according to the CMS/blog manual.

Online Installation Manuals

A summary of a variety of CMSes is available at: opensourceCMS.com.

Installation Tips

  • Vulnerabilities are regularly detected in many CMS and blog components. It is important that you deactivate all unused components in the administration section. After this, you can safely delete the relevant folders from the FTP. It will also be necessary to check periodically if a new version of the package used is available.
  • Only assign write permissions to folders that need them for a specific purpose.
  • Deactivate and delete unused components.
  • The PHP setting register_globals is set to off on all servers. You can check this by putting a phpinfo.php script on your website. Save the following code as phpinfo.php and upload it to your webspace:

Joomla 1.5.x SEO and ISAPI Rewrite version 3

To configure Joomla 1.5.x SEO (Search Engine Optimization), SEO SETTINGS must be activated in the Joomla administrator back-end. Go to:
Website -> General settings -> Website -> SEO settings

Configure the settings as follows:

  • Search engine-friendly URLs: Yes
  • Use Apache mod_rewrite: Yes
  • Add a suffix to URLs: this selection is up to you; it adds .html after the file name, or leaves it off.

The following should appear in file configuration.php:

var $live_site = 'http://www.example.com';

where “example.com” should be replaced with your complete domain name if Joomla has been placed in the main folder.

Rename the provided file (htaccess.txt) to .htaccess via FTP. This is a standard function in ISAPI_Rewrite version 3.

Joomla 1.5.x FTP layer

After the FTP layer has been activated in the Joomla administrator back-end, copy the following to your configuration.php file:

var $ftp_host = ''localhost''; // of
var $ftp_port = ''21'';
var $ftp_user = '''';
var $ftp_pass = '''';
var $ftp_root = ''/example.com/www''; // /eventueel/pad/naar/joomla-installatie

where “example.com” should again be replaced with your complete domain name.

Furthermore, it is important to include complete paths for var $log_path and var $tmp_path in configuration.php:

var $log_path = 'D:wwwexample.comwwwlogs';
var $tmp_path = 'D:wwwexample.comwwwtmp';

WordPress Permalinks and ISAPI Rewrite version 3

Permalinks are permanent links to individual weblog posts. The following (ISAPI_Rewrite version 3) .htaccess rewrite rules translate the rewritten URL and forward it to WordPress:

RewriteEngine On

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]

For more extensive blogs, more extensive rules may be needed. These rules assume that WordPress is located in the root folder (“/”). If you put it somewhere else, change the path (for instance, change “/” to “/blog/”).

Magento: Authenticated SMTP with TLS Encryption

In order to send emails with Magento via smtp.vevida.com with authentication and TLS encryption, a “ASchroder_SMTPPro” extension must be installed first.

  • Log in at http://www.yourdomain.ext/downloader/
  • Download and install the ASchroder_SMTPPro extension.

This extension is configurable in the Magento Admin panel:

  • Enable SMTP Pro Email: Yes
  • Use Store Email Addresses for Reply-to: Yes/No
  • Authentication: Login
  • Username: yourname@yourdomain.ext
  • Password: ******
  • Host: smtp.vevida.com
  • Port: 25
  • SSL Security: SSL TLS
  • -> Save configuration -> Run self-test

osCommerce or Zen Cart gives a permission error message.

If osCommerce gives the following error message:

Warning: Ik kan het configuratie bestand: ‘ d:wwwinlognaam.comwww… ‘/includes/configure.php beschrijven. Dit is een potentieel risico – Stel de user permissies goed in.

Or in English:

Warning: I am able to write to configuration file: ‘ . d:wwwinlognaam.comwww… . ‘/includes/configure.php. This is a potential security risk – please set the right user permissions on this file.

Contrary to what the error message implies, the permissions for file configure.php are in fact good. However, osCommerce uses an is_writable() functie, which cannot determine whether or not a file is writeable on Windows servers.
Whether or not osCommerce performs this check is determined by a constant definition in file includesapplication_top.php. Search for line:

define('WARN_CONFIG_WRITEABLE', 'true');

and change ‘true‘ to ‘false‘ to deactivate this error message.

If you are using Zen Cart, you will find the function in file includesinit_includesinit_header.php.

osCommerce Configuration File

In the osCommerce configuration file, it is important to indicate your domain name as HTTP_COOKIE_DOMAIN:

define('HTTP_COOKIE_DOMAIN', 'www.example.com');

Or nothing:

define('HTTP_COOKIE_DOMAIN', '');

If localhost, for instance, appears here, then your website will not function properly.

This can be configured in file /includes/configure.php.

« Back