X3 Photo Gallery Support Forums
Good to know thanks. May I ask what hosting package you used that was working like this, and that costed that much? I have seen this issue before, but mostly custom servers, not pro shared hosting. Using NGINX to serve static files (without passing to Apache) is a fair concept in itself. But requiring all requests that end with JPG (or any static file type) to be a physical file path, without forwarding to Apache, is blocking all virtual requests. That means we would need to revert to PHP parameter style to make image resizing work (ex. /x3_resizer.php?path=/path/file.jpg&w=300), which is a bit outdated and would cause issues with caching. Even our servers at Flamepix are using NGINX in front of Apache, but all requests are still by default forwarded to Apache, which handles the required processing.melisamy wrote:Inmotionhosting told me it was not reasonable to make the edits to their server because it was a shared server. They invited me to upgrade to a private server that they would be happy to make ready for X3. This would of course cost much more per month and they would also have to charge me for the customization as this was not within normal standards.
I politely asked them for a refund and cancelled $800.00 worth of hosting. A word to the wise: "If you like X3, you might want to steer clear of inmotionhosting."