| Author | Post |
|---|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Sun Oct 14th, 2007 11:05 pm |
|
Hi!
I have used editWrx on another domain in the past (two years ago) and purchased a full license. From memory, I don't remember many problems from that installation. However, I have downloaded the latest version to install on another domain, run the installer file and I get the error:
Your server does not have a usable environment variable for determining your site's root path
/hsphere/local/home/'username'/'domain.net.au'/editwrx/library/routines.txt does not exist
I think it may have something to do with the fact that I wanted to set it up to work in a sub-directory (called test) initially. I say this because one of the environment variables output to screen after this says:
DOCUMENT_ROOT=/hsphere/local/home/'username'/'domain.net.au'
I would have expected the following instead:
DOCUMENT_ROOT=/hsphere/local/home/'username'/'domain.net.au'/test
as test is the name of the sub-directory which will effectively become my new temporary Root folder.
I have sent an email to support but no response. Can anyone shed any light on this? I am using Apache.
Cheers
Michelle
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Mon Oct 15th, 2007 01:35 am |
|
Michelle
We did a Plesk update to our server and DrWeb was eating all of our emails for about 30 hours before we got him back in his cage. Sorry about not getting your email.
Your problem:
EditWrx relies on the server's environment variables for paths to itself and all other files. You therefore can not just pretend that your DOCUMENT_ROOT is somewhere other than where Apache says it is.
EditWrx can read Apache's environment variables but not your mind - unless you help it. What you need to do is override Apache's DOCUMENT_ROOT variable with one of your own. Fortunately there is an easy way to do that.
On the third line in wrx.cgi place a line containing
BEGIN{$ENV{'DOCUMENT_ROOT'}='/hsphere/local/home/username/domain.net.au/test'}
change "username" & "domain.net.au" to fit your circumstance.
That will effectively tell EditWrx that your domain starts inside the "test" directory, and it can find routines.txt at
/hsphere/local/home/username/domain.net.au/test/editwrx/library/routines.txt
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Mon Oct 15th, 2007 02:12 am |
|
Keith
That gets me further along. I can get the welcome page but notice the images are crossed out. I assume there is still an issue of paths to the images folder. When you said the third line I took that literally. ie. line one is path to perl, line 2 is blank and then line 3 is the line you suggested with the old line 3 becoming line 4.
When I login as a user, I just get a crossed out image at the top left too so something still isn't quite right with paths. I'll shoot you some login details to the server via the support form as that might make it a heck of a lot quicker for you to figure it.
But thanks for getting to this quickly (once you knew I had a problem).
Cheers
Michelle
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Mon Oct 15th, 2007 02:22 am |
|
Keith
I just added the following to my server via the server admin panel for CGI directories:
/test/editwrx -> /test/editwrx 
It already had:
/cgi-bin -> /cgi-bin
I am seeing a banner now across the top but images are crossed out still with nothing else showing on the page.
Cheers
Michelle
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Mon Oct 15th, 2007 05:00 am |
|
OK, I thought that half-through
I FTPd to your domain and added another line to wrx.cgi
BEGIN{$ENV{'HTTP_HOST'}='yourdomain.net.au/test'}
That gets the host and root pointing to the same place. Images show up as expected.
There are 2 other ways to do this nested root trick so if that doesn't work, let me know. BTW, I moved wrx.cgi to the /test/editwrx folder and it executes ok.
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Mon Oct 15th, 2007 05:44 am |
|
Keith
I should have given you the editWrx login details so will shoot them to you directly. Now it just hangs on login. I did look up the wrx.cgi file and noticed that on the first new line of code added there was a missing semi-colon at the end and the second new line added had the semi-colon inside the curly bracket. I think they both should have semi-colons at the end but I am not a coder. I also moved back the wrx.cgi into the cgi-bin directory just in case there was something funny going on there but it doesn't appear to have made a difference. At the moment it is sitting in cgi-bin.
But I think you can see what I'm trying to achieve. We are re-working the current website so I am trying to set up a temporary directory /test as a working root directory for the new website. Once I get the templates up and running with the agreed page structure, I want the client to be able to get in and edit until they are happy with the content. Once that occurs, I want to then move the new website live by shifting it to the formal root directory. I will also need to reverse any editWrx configuration changes to allow the client to continue using editWrx but in the new client site at the root level and not /test leve.
Any other ideas greatly appreciated.
I'll get those login details to you.
Cheers
Michelle
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Mon Oct 15th, 2007 06:04 am |
|
Keith
Strange errors being received in the error logs. Check them out. FTP to logs.
Cheers
Michelle
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Mon Oct 15th, 2007 03:04 pm |
|
We are re-working the current website so I am trying to set up a temporary directory /test as a working root directory for the new website
That will cause a problem later on. URLs for images and links will be resolved as http://domain.com/test/whatever.jpg instead of http://domain.com/whatever.jpg when you go live. There is a MUCH better, and standard, way to do a temporary development site, using a subdomain.
Create a subdomain: http://test.domain.com in the H-Sphere control panel. Then put all of your site files at http://test.domain.com and install a regular installation of editwrx at http://test.domain.com/editwrx. While working on the test subdomain be sure to use only virtual or relative URLs for images, links, etc. In the editwrx Site Parameters be sure to set URLs to relative or virtual path instead of full http path. As you develop the new site at test.domain.com image and link urls will not contain the hostname http://test.domain.com, just the paths.
When you are ready to go live with the new site, transfer all files at test.domain.com to the regular site directory and all will work. You will need to re-install editwrx as normal in the live domain. The editwrx domain license should work on the subdomain since the license does not reference a subdomain, just the domain.
Using a subdomain is how I do re-development of a site. It really makes re-development easy because the new site files have the same ownership as the regular domain and all paths will automatically work when you go live.
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Mon Oct 15th, 2007 10:57 pm |
|
Keith
Ahhh - an even better solution. I'd almost convinced myself I'd need to use some other bulk host space I have to set up something but the sub-domain is an excellent idea. Not sure why it hadn't occurred to me. Only trick is I'm not sure whether it is a 'free' option under the current hosting for my client but I'll look into it.
Thanks for your work on this. A sub-domain is a much more seemless solution as a staging server. It resolves the pathing issues that you point out. It dawned on me only whilst driving back from my last appointment that I'd have to remove /test from all my include files, etc. if I went the sub-directory way anyway which would be added work and likely to bring in additional problems.
Cheers
Michelle
|
Current time is 05:00 pm | |
|
