Hi Dan. I was in fact looking into this post recently regarding new features to diagnose issues, and fail-safe X3 setup. I will need to address what you last mentioned last, because unfortunately this is the main pitfall in your case:
timberline wrote:I see that much of the documentation centers on Linux as well as things such as modules specific to Apache rewrite, deflate etc. . . Is x3 supported using IIS on WIndows? If it is can you provide any guidance or documentation that could help me to ensure all of the appropriate settings are configured and pre-requisite software is available?
Yes you are right that the main focus is around Linux->APACHE server, since 99% of public hosting services use this (unless requested otherwise). Technically, X3
should work properly under windows also, as long as PHP is operational, but there are a few crucial factors that we have not yet been able to address. Most importantly, there is a crucial
.htaccess file (apache/linux), which X3 depends on to rewrite pages and create "nice url's", and also for calling upon resized images. I apologize that you were not notified about this previously, as I should have noticed it when diagnosing.
Unfortunately, I have to say that X3 just isn't ready for Win IIS servers currently, until we have the time to look into it, and prepare optional configuration. If you could offer FTP access to the Win IIS server, I would be happy to look into it rather soon ... If you cannot provide this, which is understandable, we will eventually be looking into it as soon as we find time and resource.
Just quickly going through your other points, which are mostly out-shadowed by the issue above:
timberline wrote:1 - The server has various versions of PHP installed to support older software including some older Imagevue. However we have the newest PHP clear back to the older 5.3. All we need to do is configure the individual site for the desired version of PHP. This is done.
Yes. Generally nothing wrong with this aspect. I see your host was using PHP 5.3.6, and it would definitely be
better if you were using version 5.4 or higher ... There are some issues with 5.3 regarding encoding and a few missing features.
timberline wrote:2 - The JSON files are not missing. JSON isn't a file type served by IIS by default. This was easy enough to fix.
Ok. The server should definitely be serving all typical web-formats though ... This is crucial to ANY web application. I don't see why any web server would not serve json files by default, unless it is a custom server setup from scratch (which means problems).