Hi David,

Thanks for your quick reply.

My hosting provider uses Linux servers with Apache webserver software.

I did give a different prefix than the mambo install. I used as prefix for the wolfcms installation: "wolf_" and after an second try "wolf" (without the quotes) both where giving the same result. I checked after install of there where new tables in the database, but unfortunately there where'd any.. the mambo installation has an "mos_" prefix.

Hi Martijn,

Hmm that's strange. I tried a new installation and at the first attempt the configfile is empty and 0 bytes. After a second attempt the config file was no longer empty and  approx. 4 Kbytes.

Hereby the data from the config.php file. For security reasons I altered some data like databasename and password for example before pasting it in this forum. I checked this data before altering and the data was correct. As database name I used the one that was already created for the mambo site.

<?php

// Database information:
// for SQLite, use sqlite:/tmp/wolf.db (SQLite 3)
// The path can only be absolute path or :memory:
// For more info look at: http://www.php.net/pdo

// Database settings:
define('DB_DSN', 'mysql:dbname=mydatabasename;host=127.0.0.1;port=3306');
define('DB_USER', 'dbusername');
define('DB_PASS', 'dbpassword');
define('TABLE_PREFIX', 'wolf_');

// Should Wolf produce PHP error messages for debugging?
define('DEBUG', false);

// Should Wolf check for updates on Wolf itself and the installed plugins?
define('CHECK_UPDATES', true);

// The number of seconds before the check for a new Wolf version times out in case of problems.
define('CHECK_TIMEOUT', 3);

// The full URL of your Wolf CMS install
define('URL_PUBLIC', 'www.mysiteurl.nl/nieuwesite');

// Use httpS for the backend?
// Before enabling this, please make sure you have a working HTTP+SSL installation.
define('USE_HTTPS', false);

// The directory name of your Wolf CMS administration (you will need to change it manually)
define('ADMIN_DIR', 'admin');

// Change this setting to enable mod_rewrite. Set to "true" to remove the "?" in the URL.
// To enable mod_rewrite, you must also change the name of "_.htaccess" in your
// Wolf CMS root directory to ".htaccess"
define('USE_MOD_REWRITE', false);

// Add a suffix to pages (simluating static pages '.html')
define('URL_SUFFIX', '.html');

// Set the timezone of your choice.
// Go here for more information on the available timezones:
// [url]http://php.net/timezones[/url]
define('DEFAULT_TIMEZONE', 'UTC');

// Use poormans cron solution instead of real one.
// Only use if cron is truly not available, this works better in terms of timing
// if you have a lot of traffic.
define('USE_POORMANSCRON', false);

// Rough interval in seconds at which poormans cron should trigger.
// No traffic == no poormans cron run.
define('POORMANSCRON_INTERVAL', 3600);

Last edited by niels (2010-08-31 12:32)

My hosting provider is one.com

I did not logged a ticket yet by my hosting, but could try this.

Hmm... the config file doesn't look bad. You could try replacing 127.0.0.1 with localhost... some hosting providers have issues.

The installer giving you a blank screen is a bit strange since its supposed to give you proper error messages. The fact that its blank suggests that PHP is quitting due to some coding issue.

You *are* running a very new version (5.3.3) which I'm quite surprised about. Didn't think hosting provider were that quick to adopt newer versions. Anyway, it could be a compatibility issue with 5.3.3. I simply haven't tested it since I don't have 5.3.3. locally.

If you're up for helping with testing this theory, try inserting this line just before the comments mentioned in do-install.php and then run the installer again:

echo 'TEST 1';
// If DB is SQLite, check that DB directory is writable.
.....

echo 'TEST 2';
// Try creating a new PDO object to connect to DB
.....

echo 'TEST 3';
// Run the SQL to setup DB contents
......

You should be seeing all three in a working system, but if there is a code issue, I suspect its in between these.

Hi!

I'm experiencing the same kind of problem that niels was describing but I get a empty installation result (it's the same layout only it's missing all the content in the white box) page just seconds after i press the install button.

Data:

PHP 5.1:    PHP 5.2.9
PDO supported:    true
PDO supports MySQL 1):    true
PDO supports SQLite 3 1):    false
Config file exists 2):    true
Config file is writable 2):    true
Public directory is writable 3):    true
Clean URLs support available 4):    false

MySQL - 5.0.58-log
Running on apache server

I've installed it before locally (using mamp) and it went fine but now as I'm trying to install it in a subdomain on my webspace it just fails. I tried changing localhost to 127.0.0.1 without any luck. The database configuration was also correct, I tripple-checked it.

When i check the url of the site it displays nothing but an empty page and when i look at the database it is empty.

I'm pretty stuck, any help is appreciated.

Last edited by matu (2010-09-15 16:30)

Andrew was slightly faster in responding.

You didn't mention it, but was the config.php file filled properly or is it still empty?
Also, are the DB tables create and empty or iare the DB tables also not created?

Andrew is right about the DB settings by the way. These settings differ per hosting provider and range from specific IP addresses or machine names to "localhost" or "127.0.0.1".

Sorry for not being clear enough, I'm installing it on a live site. Was using localhost as host because that's what I've used for installing every other CMS (wordpress, textpattern, silverstripe) there.

Didn't get debug to give me any further information

The config.php file was properly filled and the DB tables were never created

PS. I went and installed wordpress and enterd exactly the same values that i gave wolfcms and wordpress installed nicely...