Adding a comment field in 2.9.9.x cart not working anymore as in 2.6.x: how to?

[SteP[IT]]

Hi all
I have a question regarding the possibility of adding a comment field in cart view.
If I'm not wrong, in all previous < 2.6.10 versions, adding a comment field in cart was as simple as adding this:

Code Select Expand

<div class="customer-comment">
<span class="comment"><?php echo JText::_ ('COM_VIRTUEMART_COMMENT_CART'); ?></span><br/>
<textarea class="customer-comment" name="customer_comment" cols="60" rows="1"><?php echo $this->cart->customer_comment; ?></textarea>
</div>
I have tried to do the same in 2.6.12 and 2.9.9.x, but it seemes that it's not working anymore: it seems that something has been changed.
Is there a simple way to add again a comment field in cart without rewriting core code?
Thank you in advance

[Milbo]

Yes, because it is now all configurable. Edit your shopperfields. there should be comment box, just make it visible in the cart and done!

[SteP[IT]]

GREAT. it works
I have a small suggestions: there are a lot of possible options to implement, but the first one I need is the possibility of showing each cart attribute depending on the user group.
In my case, I have to show some fields we collect only when the user belongs to one or more specific group. It may be done by templating (and now I have made this to get the desired results), but I think it could be faster to flag the attribute in the right way by assigning the user group in the attribute config option tab and let the system do the rest.
Have a great w.e., and thanks again for your hard work.

[Milbo]

check the tos field,... you can now create easily your own fields!

[bluezeyes]

Milbo just a small thing,   the language string in the type list for custom user fields are still not translated in back end. In the English language files.

and second when I add a generic child variant or a child variant to a product,  I get lots of xpath errors in the back end on the custom fields Tab of a product each time I open the tab to edit it.. 

Third the custom field options "d" and "o" are still not or extended to "disabled" and "overwrite".
This still exist since the last joomla! Day workshop in September <have still the sentences in mind from the youtube-video>

I know these are all small things and surly easy to fix..  Either from user or the Dev team.. 
I prefer the Dev team..  [emoji6] otherwise it's a waste of time to create overwrites or copy over the language files on and on..  Instead of concentration on the real things.. 
And last it gives a better impression of a stable system without all these little annoying things for the first time user..
Even it don't affect the functionality at all jenkinhill  would state :-P

All happened on a plain vanilla VM 3.0.2, joomla 3.3.6, php 5.6.?? System


Kinds regards