Hmmm, seems like some strange behaviour. Thanks for reporting - I'll try to replicate the issue in our test environment and bugfix it for the public version 1.63 release.

As stated on every Support page we'll try to handle all support tickets within 48 hours, depending on the complexity. It has not been 48 hours, yet and we are working on a good working solution.

Because a workaround is only temporary and we want to prevent you from altering things once a final fix is released we prefer to implement a good solution.

So please have a little more patience and we'll send a personal working version to you by email.

A new version of the ReqText plugin is send to the email address registered to your account. This is the version which will be released today on our website.

It contains several updates and fixes including a fix for the problem described in this ticket.

This is strange issue - cannot seem to replicate the issue and should not happen. We'll test more intensively and if needed correct/rewrite the code for it.

Your description will do for now. Thanks.

When you check http://demo.uwix.nl, which has ReqText version 1.63 installed, we've setup the situation as described in your report:

1. Set one custom field to required in the product backend.
2. Set a second custom field to not required in the product backend.
3. Set a third custom field to required in the product backend.

When adding the product to the cart; the first and third item report to be "required". We've tested it with several types of custom fields in random order but cannot seem to replicate your described issue.

What type of fields are you using - is it possible for you to let me know the exact field configuration and order for the product you're experiencing troubles with? Maybe it's just some type of strange field/config combination that triggers the issue.
Because of the many combination which are possible it might be better to try to duplicate your exact custom field settings :) Thanks.

p.s. it will take some time before our changes to the demo site are visible. This is because of the set reset rules for the demo pages ;)

Noticed the same picutes indeed :) But, used the information to add it as new custom reqtext fields in a clean Joomla! and VirtueMart installation with sample data.

Everythings works fine in our environment: the middle field is not required and is not marked as such. The first and third custom fields get a nice "Required" tooltip and adding to the cart is not possible.

Last week I experienced an issue where code changes didn't make a difference in the front-end. No matter if I changed default VM settings of Custom field settings for the test product - nothing was showing up correctly. I removed the field(s) from the product and added them (after saving without any customfield) and all worked fine.
Some sort of caching I guess - didn't had time to look into it and I realize it isn't a very good solution. At first glance it does not seem related to a particuler plugin (ReqText or other custom field type).

As said; using the settings you've uploaded in the pictures work fine in our test case - similar like on our demo.uwix.nl site.