All of the new functions look interesting to me in one way or another. Good stuff.
But what I most want in terms of code right now is an increase in stability. I’ve become very wary now of putting any time into developing my database at the moment, because I’ve got this gut feeling of not trusting the system not to fall over again taking my work with it, with me not knowing how to get it back (see “404s everywhere” bug report.)
I realise that some people do urgently need one or more of the new functionality features and would take them in preference to bugfixes and more documentation. Just saying that wouldn’t be my personal top wish at present.
I am happy to see that magento opened up the trunk for the upcoming 1.1 release. This is a great way to keep the community engaged and make business decisions based on whats about to come. With that said, I have been holding off launching my clothing store thru magento because of the lack of a good way to load inventory with multiple attributes (size, color, etc...). The new version has me a little confused. When the community requested features that would allow multiple attributes (size, color, etc..), we were told that the bundles feature was being developed. However it seems like custom options is the optimal way for my ecommerce segment. What is magento’s position on custom options vs. bundled products and what do you and the community recommend for my segment?
Note on the (great) addition of tax number/VAT number for customers:
The EU requires to do an initial validation of tax number of the customer (’s company). After validation by local tax office, products can be purchased tax-free by the customer. This requires:
-customer being able to indicate he wants to use his tax number (during account creation probably)
-be notified that a customer has registered that requires tax number validation
-mark a customer as ‘validated’
-making sure that the customer cannot change his tax number at a later stage, because only for that number he has been validated
The first 3 items can be worked around easily, but the customer should not be able to change the number I guess. In the current 1.1 revision, this is the case.
Anyone else suggestions, or maybe experience from oscommerce etcetera?
Guess you havent tested the Export/Import-functionality in the new version, because that doesnt seem work at all. Our developer wrote himself around it, but there’s a clear bug in the Abstract-file which causes the export/import of items using the Profiler to stop (variable/array-error).
Either I’m misunderstanding what Virtual Products are, or I’m just too stupid to figure out where to say what files are included with this virtual product. Is there any documentation of how to use this feature?
Either I’m misunderstanding what Virtual Products are, or I’m just too stupid to figure out where to say what files are included with this virtual product. Is there any documentation of how to use this feature?
Virtual products and downloadable products are not the same thing. Virtual products just means a product without any attached item that is being sold.
It would also be REALLY great to get the mostly-wanted feature where we can change the Attribute_Set the product was originally created on. Guess lots of people would want that.
