mtk wrote:

in other words: don't use CB Subs yet... (?)

No, of course that's not what I am saying. Simply put only a select few fields will not function when hidden AND required.

If not required will function perfectly fine. See previous post for small list of what field types won't function properly.

mtk wrote:

krileon wrote:

If not required will function perfectly fine. See previous post for small list of what field types won't function properly.

yes I saw that, but that's a basic CB function that cease to function, so in my case, paying for CB Subs to go backward doesn't really help...

I'm sorry, we are talking about a commercial extension with a very high price (min. 100E) in comparison to other commercial extensions (around 20$).
for that price I expect a lot more.
I hope you understand why I don't understand 'feature addition before a major bug fix'.

Sorry, you're still misunderstanding my posts and reading between the lines. Please do understand only SPECIFIC fieldTYPES are having this issue. The fields are: Image Fields, File Fields, and Fields with REGEX validation. The reason is they do NOT have Javascript validation, but rather refresh the page for additional code to fire for validation. In addition to this they must be REQUIRED in order for this issue to be present.

The feature addition is the first feature release we've provided as of yet; all previous releases have been bug releases. It was simply what was planned. I apologize if this has inconvenienced you, but I assure you the issue will of course be addressed.

We're doing our best to ensure all issues are being addressed accordingly in a timely fashion, but unfortunately the day is limited by the hours it contains.

Please for the time being do not use required image/file field type fields or fields with regex expression AND are required when hiding fields via a plan. Simply setting them as non-required would result in the issue being resolved. I know the temporary workaround may not be acceptable in all use cases, but is the best approach for the time being.

Let me just chime in here shortly:

We do understand that this bug, even if affecting only specific field types, can be annoying or even blocking for your project.

It has been added to CBSubs as a "nice to have" feature, and its use has been quite more extensive than we thought initially.

So: we are planing to fix this bug with upcoming CBSubs 1.1.

To be clear: Features release does NOT mean "no bug fixes", just that bug fixes is not the sole purpose.