Incorrect handling of mandatory fields

Created on 4 March 2023, almost 2 years ago
Updated 2 March 2024, 10 months ago

How can a module development team be so undemanding?

There are also modules that are much more complex and require more knowledge than this module, and they work flawlessly.

This is still only an alpha version since 2015.

And don't let anyone ask why I'm commenting if I haven't posted a module yet. I'm not that good at it yet, but I'm happy to test it. However, if I give something out of my hand, then that's good.

Mistakes:

1.
Allows you to save the unfilled mandatory field if it does not have to appear due to the condition, but a series of error messages when deleted:

"
Notice: Undefined index: error conditional_fields_form_validate() (...) /conditional_fields/conditional_fields.module 797
Warning: array_diff(): Expected parameter 1 to be an array, null given conditional_fields_form_validate()
Warning: Invalid argument supplied for foreach() conditional_fields_form_validate()
"

Therefore, it cannot be marked as a mandatory field in the field setting, but must be set with another module, the Field Validation module.

2.
In principle, it fills a given field with a value, but in reality it does not work. But that's just a shortcoming.

🐛 Bug report
Status

Postponed: needs info

Version

3.0

Component

Code

Created by

🇭🇺Hungary atomi

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @atomi
  • Status changed to Postponed: needs info 10 months ago
  • 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    How can a module development team be so undemanding?

    How can somebody using Open Source software for free be so unwilling to learn more about what it is? And awaiting that somebody is solving the issue you have? What about providing a solution or a patch or anything helpful despite of complaining?

    The "development team" is you. Maybe you should read about Open Source more before pointing fingers at others in issue queues.

    And don't let anyone ask why I'm commenting if I haven't posted a module yet. I'm not that good at it yet

    Oh - so you actually you have no clue what you are complaining about, I see.

    Apart from that: wron prio status. Descriptions of the Priority and Status values can be found in the Drupal project issues documentation.

    And finally the whole report is - apart from complains and confusing phrases - missing details and clear description of the actual issue and how to reproduce it.

Production build 0.71.5 2024