How to Set $WAGLOBAL_Root_URL
I want to configure PowerStore so that users navigate to MyDomain.com/store
How should I set the paths for $WAGLOBAL_Root_URL and $WAGLOBAL_localRoot
I want to configure PowerStore so that users navigate to MyDomain.com/store
How should I set the paths for $WAGLOBAL_Root_URL and $WAGLOBAL_localRoot
$WAGLOBAL_Root_URL = "http://MyDomain.com/store/" ;
$WAGLOBAL_localRoot = "/store/";
$WAGLOBAL_remoteRoot = "/store/";
This would be a good example to add to the manual. Saves a lot of experimentation.
I've done that and I'm still getting HTTP 500 Error
Most likely causes:
•The website is under maintenance.
•The website has a programming error.
I have put all the modules and folders in the respective /store directory.
What else may I have over looked?
--------------------------
Agreed, it would be great to put that information in the Getting Started, somewhere near the top, since I'm assuming most people already have a working site and it seems logical to lay it out that way.
Are you testing locally?
This is a generic error message that your webserver is returning. To determine what the problem is a more meaningful error message will be needed. To enable the more advanced error messaging in IIS 7 for Vista you will need to do the following:
1) Go to Control Panel > Administrative Tools
2) Open the IIS control panel and open the ASP option
3) At the top of the ASP control area select Display: Friendly Names
4) Now go down to the Compilation area and expand Debugging Properties
5) In debugging properties make sure to set Enable Client -side Debugging, Enable Server -side debugging, and Send Errors to Browser to TRUE. Make sure to click the Apply on the right side of the page.
6) After setting the debugging you must go back to the IIS control panel and using the controls on the right side restart the server.
This will enable debugging info to display when an error occurs. This should be turned on while testing and should not be left enabled for a live server.
I am testing directly on the Windows 2003 Server. It is in my building.
You will need to enable the debugging information in the IIS Server as outlined previously to return the error message for debugging.
I'm using Server 2003 and my tabs don't look anything like you describe.
Could you please go over the configuration for Server 2003
Thanks In Advance
I dont have a Windows Server 2003 box for reference. What version of IIS is installed? this is more important than the OS version,the IIS interface is the same regardless of OS.
Do you have the Show Friendly HTTP errors setting turned on in IE?
In IE go to Tool -> Internet Options. Click the Advanced tab un check the option to "Display Friendly HTTP Error Messages"
Windows Server 2003 comes with iis 6
I checked and I do have Show Friendly HTTP errors enabled in my browser.
Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.
These out-of-the-box solutions provide you proven, tested applications that can be up and running now. Build a store, a gallery, or a web-based email solution.