Problem With Apache Config File http://dev.wikidot.org/forum/t-42017/problem-with-apache-config-file Posts in the discussion thread "Problem With Apache Config File" http://dev.wikidot.org/forum/t-42017#post-109440 Re: Problem With Apache Config File? http://dev.wikidot.org/forum/t-42017/problem-with-apache-config-file#post-109440 Tue, 19 Feb 2008 03:44:36 +0000 Ed Johnson 38854 I think I just found the problem. bin/config.php was not finding the apache.vhost.wikidot.conf file and couldn't update the variable names. I have fixed my script and am running another test install.

Sorry for being such a pest! I'm under some pressure at work to get a Wikidot install running on our internal network and have been testing like crazy at home to make sure it will work as well as your hosted site. I must be over 20 test installs now since you released Wikidot to the open source community.

-Ed

]]> http://dev.wikidot.org/forum/t-42017#post-109307 Re: Problem With Apache Config File? http://dev.wikidot.org/forum/t-42017/problem-with-apache-config-file#post-109307 Mon, 18 Feb 2008 23:06:19 +0000 michal frackowiak 1 As far as I can see the configuration scripts in wikidot1/trunk have not been touched recently… http://svn.wikidot.org/svn

]]> http://dev.wikidot.org/forum/t-42017#post-109205 Problem With Apache Config File? http://dev.wikidot.org/forum/t-42017/problem-with-apache-config-file#post-109205 Mon, 18 Feb 2008 18:32:04 +0000 Ed Johnson 38854 Michal,

Unless I made a mistake in my install script, it appears you made a change in the last day or two to the distributed apache.vhost.wikidot.conf file that causes the Apache server to fail upon startup.

Some of the new %{WIKIDOT:xxx} variables don't appear to be getting set properly somewhere. When I reverted back to the older version of the config file, things started working again.

Are there new steps that need to be added to the Debian/Ubuntu install guides?

Apologies if I made the mistake - my install scripts were working well 2 days ago and I only made minor changes that should not have caused this, but maybe I missed something.

Thanks,
Ed

]]>