From MY point of view, this is definitively NOT critical issues !
1) The port number IS NOT HARD CODED !!! The module simply ignore them. I already explain this to you here.
2) Same explanation that for the first point. This two ones are NOT SO CRITICAL, because A LOT of smtp servers DO NOT USE SSL and use the STANDARD port 25. Moreover, if you click on the question mark near the setting "SMTP Server" (Host > Configuration > SMTP Server Settings), you can read: "Enter the SMTP Server Address, you can also specify an alternate port by adding a colon and the port number (e.g. smtp.googlemail.com:587)". In this case "alternate" is a port number different than 25. In other words, when you use a standard smpt server on port 25 without SSL, you are NOT impacted by this bug. In fact, only 2 users (you included) have encounter this problem. Considering that the Store module was downloaded 7556 times, only less than 0.0003% have experienced the bug. This is why I SAID: IT'S NOT CRITICAL. It's a problem, I agree, but NOT CRITICAL. We do not have the same dictionary, that's all.
3) Off course the status order are hard coded! It's normal, because it's not only strings. There is a little bit of logic behind them. As a sample, a user can cancel an order IF AND ONLY IF the status order is: Awaiting Payment, Awaiting Stock and if the Store Adminstrator have checked the setting "Authorize Cancel". When you post about status order (here), I suggested to rename an existing string, like "Dispatched" to "Delivered" because this do not change the logic behind. If it's not enouth, you can create your honw specific version or make suggestions intead CRITICISM. A peacefull exchange is ALWAYS more productive than CRITICS! The problem is not about my "emotions" but about constructive dialog.
4) The default status IS NOT INVALID! The "Processing" status is set when the web site do not receive a response from Paypal. If PayPal callback the web site when the payment occurs, then the status is automatically changed to "Paid".
5) Currently, I work on the address provider. Only you and David have encourter this problem. I will try to reproduce it.
6) EVERY strings in the Store module can be changed via the standard DNN Language Editor. Go to Host > Language > Language Editor, then expand Local Resource > DesktopModules > Store in the left tree. From here, you can find all resource files and change them as you like.
7) This is by design and I would not change that in the next versions. Once more, there is a good reason with that. The name of the page where you placed the Store Account module is inserted in the email because the user can retreive his order history from this module. For me, it's logical! I plan to create a template for email like the one used for the catalog but not for the next versions. This will offer a little more flexibility for the configuration. But it is not a priority because there are many of other improvements to make before this one!
8) One more time, it's normal. You can't have more than one Store Menu and one Store Catalog module by portal. You'r right, the Store module could have more options. My goal is not to create the most better store module in the universe, but to offer a FREE module to those they do not have money. There is many commercial store modules with a lot of options and features, like AspDotNetStoreFront or Catalook for other needs.
9) In the next version, you will be able to sort the category product section by: Manufacturer, Model Number, Model Name or Unit Price (ascending or descending).
10) I agree and I would not change that in the next versions. Same advice for commercial modules.
11) It's false! The "Order" setting in each category is the sort order. Click on the question mark near "Order", you will see: "The order to display the category in".
Gilles