URL not found after upgrade

[Jose Ramirez]

Hi,

I just installed the latest version of domuslink. When I point to
http://my-server/domus.Link/ I'm able to see the page but with no
graphics. If I click on any of the links I get the following error
message: The requested URL /index.php was not found on this server.
Probably I'm missing something, any ideas?

Regards,

Jose

[Brad]

Do you have your web server and domus.Link set to go to the subpath you show in your post above? The default install is to the root path of your webserver  (http://my-server) and you if you have it subpathed from the root you need to make sure the webserver resolves the path and that domus.Link has the urlpath setting to /domus.Link in the config page.

Brad

[Jose Ramirez]

Hi,

Thanks for the info. I just created the following file on /etc/apache2/
sites-available:

ServerAdmin webmaster@localhost

DocumentRoot /var/www/domus.Link
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/domus.Link/>
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
</Directory>

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
</Directory>

ErrorLog /var/log/apache2/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog /var/log/apache2/access.log combined

Alias /doc/ "/usr/share/doc/"
<Directory "/usr/share/doc/">
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from 127.0.0.0/255.0.0.0 ::1/128
</Directory>

Then created a symlink on /etc/apache2/sites-enabled. After restarting
the apache server everything is working fine.

Thanks.

[Brad]

Just checking that your new config solved the problem? That looks correct above.

[telecaster]

Hello,
I had a similar problem, in v2 domus.Link seems to be installed in the
root folder as the poster says below, ie http://your ip/ and not http://your
ip/domus.Link/
I followed instructions and they say that the install is prefixed
with /domus.Link/ but it didn't happen in practise.
I also didn't see graphics. After fishing around and re-instaling, I'm
under the impression that any changes made in domus.Link are all
converted to lower case in the heyu config files. In my x10.conf I had
'Scenes' with upper case letters (and an alias now missing a housecode
for some reason) which was preventing heyu from starting under
domus.Link v2. domus.Link did not report this but by heyu not
starting, it did not display any grahics. Check heyu on the command
line (type: heyu engine) and resolve any errors it throws up and then
domus.Link should display ok.... I hope.

Now I can't see appliances or get into the setup pages, but thats
progress in Linux '98 I suppose... roll on Linux XP. I'm using part
domus.Link and part ssh via iPhone for some commands, a bit of a mess
at the moment.

Hope this helps

On May 15, 1:40 am, Jose Ramirez <j...@joseramirez.name> wrote:
> Hi,
>

> I just installed the latest version of domuslink. When I point tohttp://my-server/domus.Link/I'm able to see the page but with no

[Markus Reimer]

The change from /domus.Link to the root folder is the first line in
the change-log.
The install document don't seem to be updated for 2.x however.

BR
//Markus Reimer

> --
> You received this message because you are subscribed to the Google Groups "domuslink-users" group.
> To post to this group, send an email to domusli...@googlegroups.com.
> To unsubscribe from this group, send email to domuslink-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/domuslink-users?hl=en-GB.
>
>

[Brad]

I think there is some confusion about the install doc as I did update it. I believe the issue comes from the new config.php file that does not default the url path to /domus.link as it did before. Most of you who are upgrading need to make sure you copy the old config.php back and then go to settings and do a save on the frontend configuration. Then exit the browser and go back to your domus.link page.

I should add some wording in the upgrade portion of the install doc.

Brad

[havocist]

I'm having the same problem. The above config file didn't work. I'd
like to have domus.Link *not* be the only webpage on my server, but
there's little documentation on how to do this with 2.0. As it is,
going to to fqdn/domus.Link shows the page with no images and all
links go to fqdn/ even with the path set in the config file.

Fist post and all that. Thanks for all the work Brad. It looks like a
great product. Seems like it just needs a little better support for
other configurations.

[Homer Stanford]

I just put the whole domus-link folder in the Apache documents folder and use the URL 192.168.0.200/domus.link/
and it works like a charm.

Homer

[Brad]

You will need to set the path from the root web server in the config.php under ""$config['url_path'] = ''; setting. This tells the domus.Link app where to path in the files. This is part of the upgrade of the docs I need to do.

Brad

[Cranbo]

It doesn't work. Next guess?
 </rob>

[Brad]

What is your config[url_path] setting and where does domus.link live on your server. I will need some more info to help solve the problem.

Thanks

Brad

[Brad]

I have also updated the howto in at domus.link.co.pt for apache2.2 config for an example where multiple sites are on a server.

Brad

[Cranbo]

On Feb 19, 7:36 pm, Brad <crush...@yahoo.com> wrote:
> I have also updated the howto in at domus.link.co.pt for apache2.2 config
> for an example where multiple sites are on a server.
>

Brad,

Thanks, that seems to have given me the information I needed - I now
have dL working!

I'm running OpenSuSE 12.1, which is not a Debian-like distro, so I
have no "a2ensite" or "a2dissite" commands. All I did was create a
domus.Link virtual server file (just as you provided in the How To,
but edited to point to my dL installation at /srv/www/htdocs/
domus.Link) in the apache2/enabled-sites directory, restart the
server, and there it was!

/rob

[Brad]

Good to hear it works. The examples were in need of updating.

Brad