Broken links and incorrect display.

[GoogleCodeExporter]

What steps will reproduce the problem?

What is the expected output? What do you see instead?

Expected: Page that looks like the example screenshot. 
Actual: Broken links and images. Clicking on any links redirects to my main 
website homepage, instead of the domus link pages.

What version of Heyu and domus.Link are you using? On what operating
system?

Latest and latest. Ubuntu 10.04 LTS

Please provide any additional information below.

I checked out the Apache 2.2 setup, but it's not ideal for my needs. I wish to 
run domus in a subdirectory of my main website, in /var/www/domuslink and 
control the program exclusively from there. Doing the apache setup disabled my 
main default site. Maybe I'm missing something but I need a point in the right 
direction.

Original issue reported on code.google.com by BrandonM...@gmail.com on 7 Oct 2012 at 5:30

[GoogleCodeExporter]

Also forgot to mention that I did change url_path in config.php to to 
'/domuslink' instead of the default ''. I think getting it to stay in it's 
directory would solve my problems.

Original comment by BrandonM...@gmail.com on 7 Oct 2012 at 5:31

[GoogleCodeExporter]

So my previous problem seems to have fixed itself, dunno how I managed to pull 
that off. Now I'm getting this when trying to start Heyu from the interface:

Fatal error: Uncaught exception 'Exception' with message 'Schedule file not 
enabled' in /var/www/domuslink/lib/classes/heyuconf.class.php:80 Stack trace: 
#0 /var/www/domuslink/lib/classes/heyuconf.class.php(92): 
heyuConf->getSchedFileValue() #1 
/var/www/domuslink/lib/classes/global.class.php(167): heyuConf->getSchedFile() 
#2 /var/www/domuslink/admin/frontend.php(94): frontObject->getHeyuSched(true) 
#3 {main} thrown in /var/www/domuslink/lib/classes/heyuconf.class.php on line 80

Original comment by BrandonM...@gmail.com on 8 Oct 2012 at 12:38

[GoogleCodeExporter]

It looks as if domus is not handling a commented out sched file directive. If 
you uncomment the line in the x10.conf file with a valid file name, it will 
solve your issue for now.

Original comment by bwsamuels@gmail.com on 8 Oct 2012 at 6:05