Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 1 to 6 of 6 total |
Local server for PHP |
Sun, Sep 23 2012 2:56 PM | Permanent Link |
Eric Schwarz | I've been testing by deploying to a server that supports the PHP I need to handle my ServerRequests. I want to switch to a local test environment by using the embedded browser and an existing Windows Server's IIS. Testing the basic access, I created an html file that is hard-coded to emit the row info for a dataset. It works if I bring it up in FireFox, i.e., 192.168.1.150/test.htm display the proper text in my browser. If I change the ServerRequest to that same URL, it fails with an "Access is denied" message. Does the embedded browser prevent me from accessing another computer this way? Will I have to run a web server on my dev machine?
--- Eric Schwarz |
Sun, Sep 23 2012 10:07 PM | Permanent Link |
Raul Team Elevate | You're likely running into cross domain scripting issue - you need to serve the EWB app from the same webserver your web service back end is on. You cant use the IDE - compile and deploy the app to server hosted by your IIS server and then access app from browser. Raul |
Mon, Sep 24 2012 11:30 AM | Permanent Link |
Eric Schwarz | Kinda figured that might be a problem.
I just tried adjusting the compiler output path to send the files directly to the IIS folder and that didn't work. EWB is taking the project's base path, e.g., N:\projects\abc, and appending the output path, e.g., W:\inetpub\wwwroot, and coming up with N:\projects\abc\W:\inetpub\wwwroot. Clearly, THAT's not gonna work! I see in the docs that this is supposed to be a relative path from the project. It would be nice if there was an option for an absolute path here. Back to using deploy to test. --- Eric Schwarz |
Mon, Sep 24 2012 12:59 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eric,
<< I just tried adjusting the compiler output path to send the files directly to the IIS folder and that didn't work. EWB is taking the project's base path, e.g., N:\projects\abc, and appending the output path, e.g., W:\inetpub\wwwroot, and coming up with N:\projects\abc\W:\inetpub\wwwroot. Clearly, THAT's not gonna work! >> I wouldn't recommend doing that. You'll often run into issues with rights, open files, etc. The recommended way is to use the deploy option with a straight copy (as opposed to FTP). And, as you've seen, the output path is always relative to the project path. If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Mon, Sep 24 2012 1:35 PM | Permanent Link |
Eric Schwarz | I was just trying get a one-step compile/test thing happening.
--- Eric Schwarz |
Mon, Sep 24 2012 2:05 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eric,
<< I was just trying get a one-step compile/test thing happening. >> Understood. Not criticizing, just letting you know that EWB's gonna fight you on this one. Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, December 6, 2024 at 05:39 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |