File does not exist: /var/www/html/conjoon/default

[jpforte]

I have just installed conjoon. Note that a directory was not created with the automated install. /var/www/conjoon/conjoon_application/cache/db/metadata

Now I get a blank screen with just the background graphic. I have Fedora 12, installed the base at /var/www/htdocs/conjon and the libs and apps at /var/www/conjon/

config.ini.php says:
include_path = /var/www/conjoon/conjoon_libs
application_path = /var/www/conjoon/conjoon_application

But when I try http://localhost/conjon/

I get the error in /var/log/http/erro_log
application_path = /var/www/conjoon/conjoon_application

[ThorstenSuckow]

This is possibly related to a missing mod_rewrite module from Apache - are you sure it's installed? Did the install wizard run through without problems?

[jpforte]

yes mod_rewrite is definitely installed.

here is the .htaccess
RewriteEngine on
RewriteBase /var/www/html/conjoon/
RewriteRule (^index\/redirect.+)$ index.php
RewriteRule !(^install)|(^blank\.html)|\.(mp3|swf|js|ico|gif|j pg|png|css)$ index.php
~

[ThorstenSuckow]

RewriteBase /var/www/html/conjoon/

Okay, this looks wrong.

This is from the Troubleshooting FAQ:

Make sure the doc_path is set to it's proper value. This property can be found in the config.ini.php. If you access conjoon over http://www.somerandomhost.com/conjoon, the doc-path has to be set to /conjoon. Additionally, the property RewriteBase in the .htaccess-file has to be set to the same value.

Please adjust both values and let me know if it helps.

[jpforte]

OK. I figured that part out. The info in the config file says to use 'conjoon' however it requires the leading slash. And ditto it appears for the .htaccess file
I also had to create the cache directories by hand?

[ThorstenSuckow]

OK. I figured that part out. The info in the config file says to use 'conjoon' however it requires the leading slash. And ditto it appears for the .htaccess file

So did it resolve your issue?

I also had to create the cache directories by hand?

This might be an issue related to read/write access regarding your PHP/Apache setup. I see there's room for improvement in the install wizard when it comes to check properly for this.