Todd,
I think there is some confusion here, If you fill in http://www.yourschool.com/starnet in the URL field then the
link will show up wrong as you have noticed.
The intention was to fill in the root url there and use the
directory from the webserver path (only the right part) to
make the link.
If your site is installed in http://www.yourschool.com/cms/starnet
I strip the starnet from cms/starnet and add it to the url.
Maybe the docs should be clearer?
Thanks for your input on this.
Kind regards Fred.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understand. You're correct that the problem was with my
configuration. What I did was:
Serverpath: /var/www/html/MySchool/
starnet driectory: starnet
URL: http://myserver/MySchool
In other words, if I'm installing sas in a subdirectory (say
"mySchool" under /var/www/html), the "Server Path" should be
to Apaches root documents (/var/www/html/), not the S@S
root. The starnet directory should include the "mySchool"
subdirectory (mySchool/starnet). The URL should then point
to the servers root directory (as it says).
You're correct that I was confused. The statement "The
rootpath to Site@School, eg.:" threw me a bit. Just so
you're aware, doing this, and choosing to populate the site
with sample data creates the following link: http://myserver/MySchool/starne/index.php. Regardless of
the subdirectory being used, "starne/" is always present in
the $path variable.
Perhaps it would be worthwhile to check for the presence of
"starne/" in the $path variable and alert the user to the
misconfiguration. Having the link incorrect isn't a
problem, but having S@S configured this way breaks the image
manager as well - a slightly more visable problem. From
looking through the postings on the forum, it appears a few
others have accidently misconfigured their systems as well.
Not a big deal, especially in such a great project, but
still thought it was worth mentioning. Keep up the great work!
Todd
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Todd,
I agree this is a tricky part of the installation. that why
I gave 2 examples under the input fields.
The reason we have done it this way is because some servers
with virtual websites on it gave me back the wrong document
root path in PHP. So I decide to split it into 2 parts the
document root and the S@S directory.
I don't understand why your link failed because I strip the
starnet of the $path in line 992 : $path =
substr($userpath,0,strlen($userpath)-8) ;
So in your case the $path should have been empty? right?
Kind regards Fred
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Made sense to me! I think what's happening is since
$userpath is only 7 characters, strlen($userpath) is
returning 7. Subtract 8 and -1 strips off one character.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=512625
Todd,
I think there is some confusion here, If you fill in
http://www.yourschool.com/starnet in the URL field then the
link will show up wrong as you have noticed.
The intention was to fill in the root url there and use the
directory from the webserver path (only the right part) to
make the link.
If your site is installed in
http://www.yourschool.com/cms/starnet
I strip the starnet from cms/starnet and add it to the url.
Maybe the docs should be clearer?
Thanks for your input on this.
Kind regards Fred.
Logged In: YES
user_id=588095
I understand. You're correct that the problem was with my
configuration. What I did was:
Serverpath: /var/www/html/MySchool/
starnet driectory: starnet
URL: http://myserver/MySchool
In other words, if I'm installing sas in a subdirectory (say
"mySchool" under /var/www/html), the "Server Path" should be
to Apaches root documents (/var/www/html/), not the S@S
root. The starnet directory should include the "mySchool"
subdirectory (mySchool/starnet). The URL should then point
to the servers root directory (as it says).
You're correct that I was confused. The statement "The
rootpath to Site@School, eg.:" threw me a bit. Just so
you're aware, doing this, and choosing to populate the site
with sample data creates the following link:
http://myserver/MySchool/starne/index.php. Regardless of
the subdirectory being used, "starne/" is always present in
the $path variable.
Perhaps it would be worthwhile to check for the presence of
"starne/" in the $path variable and alert the user to the
misconfiguration. Having the link incorrect isn't a
problem, but having S@S configured this way breaks the image
manager as well - a slightly more visable problem. From
looking through the postings on the forum, it appears a few
others have accidently misconfigured their systems as well.
Not a big deal, especially in such a great project, but
still thought it was worth mentioning. Keep up the great work!
Todd
Logged In: YES
user_id=512625
Todd,
I agree this is a tricky part of the installation. that why
I gave 2 examples under the input fields.
The reason we have done it this way is because some servers
with virtual websites on it gave me back the wrong document
root path in PHP. So I decide to split it into 2 parts the
document root and the S@S directory.
I don't understand why your link failed because I strip the
starnet of the $path in line 992 : $path =
substr($userpath,0,strlen($userpath)-8) ;
So in your case the $path should have been empty? right?
Kind regards Fred
Logged In: YES
user_id=588095
Made sense to me! I think what's happening is since
$userpath is only 7 characters, strlen($userpath) is
returning 7. Subtract 8 and -1 strips off one character.
Logged In: YES
user_id=512625
Todd,
You are absolutely right, I see your point now. I will look
into it to see if I can improve the install.
Kind regards Fred.