Xenboy

It was just confirmed as part of v4.4.

It's probably not specifically about the feature set for most people, I'd guess. It's about allowing those of us with an existing Square merchant account to use it here as well. Having to use two different merchants is a serious pain and can be somewhat expensive for those who have paid for infrastructure with Square. Both Square and Stripe are popular with small business and having both would make IPS Commerce more useful out of the box.

And also take a large hit in performance, plus, storing multi-GB files in a database isn't recommended, but is something the file system can handle.

In a number of popular web scripts like Drupal, the software has the ability to specify a non-public location for the software to store and serve files from. IPS doesn't allow this, you can only specify file system locations that are within the web root of the account (meaning that there is direct access to the files via a URL). For security, best practice is to store data outside of your web root location. This stops people from uploading files and then accessing them via direct URL and potentially compromising the account or even the server (particularly on servers where the web server does not run PHP scripts as the local user). It would be nice if IPS supported local file system access outside of web root. Right now, IPS also allows you to specify a local file system storage location outside of the web root, but if you use that file storage location, those items will no longer be accessible by IPS once the system moves them. If nothing else, IPS should warn people in the ACP that if you specify a file system location outside of the web root, the items won't be accessible.

Hi, I had a problem when upgrading IPB 2.3.6 to 3.0.4 that caused me several hours of work. I upgraded successfully, but when going to the forum, all I saw was text, without any CSS or graphics. I downgraded and re-upgraded several times and tried numerous posted tricks without fixing the issue. I finally gave up, downgraded one last time and put in a helpdesk ticket. It turns out that my problem was caused because for some reason or another my server doesn't support the minify code you folks now enable by default. There were no knowledgebase items mentioning this issue and searches of the forum turned up nothing. I recommend that the installer/upgrader notify the user if the installer is unable to determine if minify or regular skins are going to be supported by the hosting environment and allow the user to make a choice of the default setting during the installation process. Something like this: The same sort of thing could be shown for the choice to use safe skins or not if the installer/upgrader cannot determine if standard skins will work or not. This would help reduce the number of tickets that people might put in.