Now that Conditional Fields 1.0 is out, we can focus on new features for the next version.

The most common problem with CF is compatibility with non-core CCK modules.
Many patches have been proposed to fix issues with single modules (like Date and Content Taxonomy), but I think that we can't simply add them to the main module, because it would become in brief bloated and unmaintainable.

The best long term solution is to add a plug-in system to CF, so every widget has its own conditional settings that allow it to work. To do this, we need to identify the things that conditional fields needs to know to guarantee compatibility.

My ideas are still not clear on the subject, so contributions – also theoretical – are very welcome.

For those looking for a solution and for those contemplating how to build it out, some consideration may give given to the Rules module and how it can solve problems. In my case, I had a controlling field to show/hide a Link field and FileField.

hello, I was wondering if there has been any further development in this area?
should we post in drupal module forum for help in this development for conditional fields?
great module and hope to see this module continue to get better!

Ok I've found a quick fix for the problem related to the validation of required non-core conditional cck fields.

It works at least for the Link module, but should work for a bunch of other "CCK field modules" too.

There was 2 problems:
- Error when the required conditional field is not visible (condition has not been triggered), asking for filling it in.
- Error when the required conditional field is visible (condition has been triggered), asking for filling it in.
So basically it was not working at all :)