VirtueMart Forum

VirtueMart 2 + 3 + 4 => Virtuemart Development and bug reports => Topic started by: toonetcreation on July 05, 2012, 09:37:32 AM

Title: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 05, 2012, 09:37:32 AM
Hello Team,

I'm running on Joomla 2.5.4 and I have tested migration from VM 2.0.6 to 2.0.8

Here are my first results (you can see the website in live mode here: http://mon-secret.toonetcreation.com/index.php/la-mode/jeans-pantalons.html):

-> Availability icon has disappeared on product details page:

With a product (in stock) with or without childs products and option field selected (for size for example)  -> the icon is not displayed.
With a product (not in stock) with or without childs products and option field selected (for size for example)  -> the icon is displayed.

NB: option field is activated with a custom fields (Plug-ins type).

See attached files called availability-icon-before.jpg and availability-icon-after.jpg

-> On back-end, the link "Create an invoice" does not work:

See attached files called invoice.jpg

-> Stock management problems:

1. When a product is ordered and then out of stock, ADMIN does not received an email to alert him that related product is not in stock anymore.

2. Stock level display in back-end is wrong (see attached files called stock-inventory-01.jpg and stock-inventory-02.jpg)
On the filter menu, if I select "Product low stock", I see only products not in stock instead of product in low stock.

3. Stock level display in front-end is wrong (see attached file called stock-level.jpg)
The icon on the front-end says "Not in stock", but I have some items in stock (e.g: 3 in S size, 2 in M size, and 0 in L size)...but the display is wrong.
A general question, how works stock management with childs products, to manage size for example?

-> User registration problem:

Even if I select all the parameters, the customer does not receive the self-registration e-mail.
And, when a customer tries to create an account on the website, he is automatically logged-in, instead of activate his account before.

See attached file called user-registration.jpg

I will update this post if I found some bugs or strange stuff.

Thanks in advance for your work and your support.

laurent


[attachment cleanup by admin]
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 05, 2012, 09:38:23 AM
Other pictures...

[attachment cleanup by admin]
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 06, 2012, 08:42:21 AM
I have seen that VM 2.0.8c is now available, do you know if issues described above are solved on this release?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 10, 2012, 09:45:39 AM
Hello,

No news about this ?

Thank you
Laurent
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: Milbo on July 10, 2012, 15:36:37 PM
Partly, I am quite sure we looked on some of them.
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 10, 2012, 16:01:49 PM
ok thank you.
do you know when a solution should be provided (approx) ?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: DaSco on July 10, 2012, 23:24:08 PM
In the version 2.0.8c is not applyed the rule associated to a category if the category is not published.

This working in the version 2.0.6.

You can try if it happens to you?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 11, 2012, 08:51:27 AM
I'm sorry I don't undertand what do you mean by "the rule associated to a category if the category is not published." ?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: DaSco on July 11, 2012, 10:56:16 AM
Sorry for my bad English..

If I set a calculation rule for a category1 and after that I set this category not published, the calculation rule doesn't work, while in vers. 2.0.6 was all ok.

For example I need to create a not published category for set a discounts of my supplier.
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 11, 2012, 11:59:23 AM
ok thanks for the info
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: Milbo on July 12, 2012, 11:54:40 AM
Quote from: DaSco on July 10, 2012, 23:24:08 PM
In the version 2.0.8c is not applyed the rule associated to a category if the category is not published.

This working in the version 2.0.6.

You can try if it happens to you?

Fixed for version d
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 12, 2012, 12:04:08 PM
If now a version d will be released, that mean version 2.0.8 is not stable ?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: DaSco on July 12, 2012, 12:56:10 PM
When it will be a very version stable?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: Milbo on July 13, 2012, 17:12:14 PM
Tss toonetcreation. You have always patches for windows, linux and mac. Why do you think it is different here? When it wouldnt be stable, we couldnt do patch releases within 3 days.

When it would be unstable, it would take a lot longer, as it did before. We did not add any new features, just fixes.
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 13, 2012, 17:52:46 PM
I said VM 2.0.8 is not a stable version because me, and a lot of people, are finding every day a lot of important bugs (e.g: stock management, user registration etc..) and from my point of view (but maybe I'm wrong), when some main features are not working, it's not stable a version.

If there are minors bugs on some specific features (not so used by the user), ok it's not so important, and we can go on.

but now, for my use, it's not possible to use correctly VM if these main features are not working properly.

And be sure that I really appreciate the hard work done by all the VM team.
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: Milbo on July 13, 2012, 22:30:49 PM
The user registration is working, but you can use really a lot of different configurations. And one of this configurations is not working, which is in fact a quite senseless configuration. Most people do not use account activation by email. Which even work as long you do not have more than one url pointing on your store.

The stock managment is working. Just the message of low stock is not always working. Again only when you have the case that you use the some special variants, for normal products with variants it works.

Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 16, 2012, 11:54:01 AM
Ok for user registration, I agree it's not a real big problem...but for security reasons (e.g to avoid SPAM) a working self-reg could be useful I think.

About stock management, I agree it works on the front-end but ADMIN does not receive an email when a product is empty.

With special variants, that mean I cannot manage my stock? so I cannot have a product in M, S or L size and manage the stock for each size?
If yes, could you please tell me how?

Thanks again for your support
Laurent
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: Milbo on July 16, 2012, 17:49:30 PM
It depends on how you organise this variants. You must use the stockable plugin or the dynamic child variants. I do not reallly understand which version is not working. In general the notify is sent, when after the stockupdate the count is lower than the configured value. Therefore it should also work for childs, but john says it does not.
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 17, 2012, 10:46:03 AM
ok so am I right with this ?

- stockable plugin : go to Products -> Custom Fields -> New -> Custom Field Type = plug-ins

- dynamic child variants : go to Products -> Custom Fields -> New -> Custom Field Type = Generic child variant
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: Milbo on July 17, 2012, 14:52:10 PM
yes
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 17, 2012, 15:14:31 PM
Ok thanks so now, if I want to manage my stock for each size for a product (e.g: tee shirt in S, M and L size) I have to:

- create the main product
- create childs products (one for each size, so 3 childs)
- link them to the main product
- create a custom field called for example options (Products -> Custom Fields -> New -> Custom Field Type = plug-ins AND plug-in = VM - Custom, stockable variants) with option name 1, option name 2, option name 3 and option name 4
- go to my main product -> tab Custom fields -> then I add the custom field created before with all the size (see attached file called custom-field.jpg)

Questions:

- Am I right again ?
- Do I have to check the boxes called Parent Variant  (see attached file called custom-field.jpg) ?
- on main product, on the tab Product status, do I have to fill in In stock and Low Stock Notification fields? or is it on childs products?
- on childs products, on the tab Product status, do I have to fill in In stock and Low Stock Notification fields? or is it only on main product?

Many thanks again.
laurent

[attachment cleanup by admin]
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 23, 2012, 14:54:53 PM
Hi Milbo, about my last post, what do you think?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on July 26, 2012, 09:13:13 AM
no news ?  :-\
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 03, 2012, 16:29:57 PM
Hello

Someone can confirm if I'm right or not with this?

Ok thanks so now, if I want to manage my stock for each size for a product (e.g: tee shirt in S, M and L size) I have to:

- create the main product
- create childs products (one for each size, so 3 childs)
- link them to the main product
- create a custom field called for example options (Products -> Custom Fields -> New -> Custom Field Type = plug-ins AND plug-in = VM - Custom, stockable variants) with option name 1, option name 2, option name 3 and option name 4
- go to my main product -> tab Custom fields -> then I add the custom field created before with all the size (see attached file called custom-field.jpg)

Questions:

- Am I right again ?
- Do I have to check the boxes called Parent Variant  (see attached file called custom-field.jpg) ?
- on main product, on the tab Product status, do I have to fill in In stock and Low Stock Notification fields? or is it on childs products?
- on childs products, on the tab Product status, do I have to fill in In stock and Low Stock Notification fields? or is it only on main product?

Many thanks again.
laurent
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: OpenGlobal on August 07, 2012, 18:09:20 PM
If you want to manage the child stock levels, then yes, you have to fill in the stock levels on the children. If the parent stock levels are irrelevant if you are managing child stock levels.

OpenGlobal
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 07, 2012, 18:45:14 PM
Ok thanks.

So that mean on the parent, in Product status tab, I type 0 in the field In Stock and 0 in the field Low Stock Notification ?

Does that mean also the stock level icon is useless ?
Because this icon is linked to parent stock level and not child stock level. correct or not?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: OpenGlobal on August 07, 2012, 18:47:58 PM
These values on the parent are ignored for the stockable cart variant.

OpenGlobal
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 07, 2012, 18:57:44 PM
OK.

So if I understand correctly we have 2 cases:

- use without childs products + without stockable car variants= stock level management works with the parent and the stock level icon is useful and working

- use with childs products + stockable cart variants = stock level is managed at child level and stock level icon is non working

And is there a possibility to display on the front-end the child stock level ?
for example with a tee-shirt in S and M size with something like that:

S = 5 items in stock
M = 4 items in stock
...
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: OpenGlobal on August 07, 2012, 20:54:36 PM
The stock level availability works with stockable variant too, but on the child level, not the parent.

If you want to display the stock levels of the children, you'll need to access the javascript.

OpenGlobal
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 08, 2012, 08:56:33 AM
Thanks for your answer.

That mean by default I can't display the stock level of the children, but only for the parent.
And as I need to manage my stock at children level (because one product can have many size), I think I will not display stock level availability on the front-end.
It would be better to use options called "Do not Display Product" or "Do not Display Product, if child products also out of stock" when a Product is Out of Stock.

Do you know if it's normal that ADMIN does not receive an email when a Product is Out of Stock (due to a customer order) ?
Is it a bug or this feature is not implemented yet ?

For my info, I have opened 2 another topics, did you encountered these problems?

http://forum.virtuemart.net/index.php?topic=106146.msg353983#msg353983

http://forum.virtuemart.net/index.php?topic=106148.msg353987#msg353987

Thanks again
Laurent
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 09, 2012, 08:26:21 AM
Quote from: toonetcreation on August 08, 2012, 08:56:33 AM
Thanks for your answer.

That mean by default I can't display the stock level of the children, but only for the parent.
And as I need to manage my stock at children level (because one product can have many size), I think I will not display stock level availability on the front-end.
It would be better to use options called "Do not Display Product" or "Do not Display Product, if child products also out of stock" when a Product is Out of Stock.

Do you know if it's normal that ADMIN does not receive an email when a Product is Out of Stock (due to a customer order) ?
Is it a bug or this feature is not implemented yet ?

For my info, I have opened 2 another topics, did you encountered these problems?

http://forum.virtuemart.net/index.php?topic=106146.msg353983#msg353983

http://forum.virtuemart.net/index.php?topic=106148.msg353987#msg353987

Thanks again
Laurent

Do you know if it's normal that ADMIN does not receive an email when a Product is Out of Stock (due to a customer order) ?
Is it a bug or this feature is not implemented yet ?
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: OpenGlobal on August 09, 2012, 09:52:49 AM
It's just not part of the functionality. If you want it, you'd probably have to code it yourself.

OpenGlobal
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: OpenGlobal on August 09, 2012, 09:53:47 AM
Or pay someone to write a plugin to do it for you  ;)

OpenGlobal
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 09, 2012, 10:00:38 AM
Ok thank you again for your help.

I suppose you will be able to do it? If yes maybe I will be interested for one of my customers.
Send me a personal message with your price to develop it  ;)

Thanks
Laurent
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: OpenGlobal on August 09, 2012, 15:24:44 PM
Ah, I've just seen your comments on another thread. I understand now. Yes this is a bug. I'm assuming that it will be fixed in the next release.

OpenGlobal
Title: Re: Migration from VM 2.0.6 to VM 2.0.8 - List of bugs
Post by: toonetcreation on August 09, 2012, 16:08:31 PM
Ok so I wait the next release.

and about this?
http://forum.virtuemart.net/index.php?topic=106146.msg353983#msg353983