Hi guys,
While working on a new feature at #2292947: Add a new condition: Link image field to content or file if target is empty, I was brought to implementing FFC API's hook_ffc_conditions_info in an external module (ffc_extra, see #2292947: Add a new condition: Link image field to content or file if target is empty).
It appears the hook allows introducing new conditions, which in turn call form and execute callbacks:
ffc_condition_form_CONDITION
and ffc_condition_execute_CONDITION
For a given CONDITION
key, for example 'hide_if_empty'
, the names of the form and execute callbacks necessarily need to be respectively:
ffc_condition_form_CONDITION
and ffc_condition_execute_CONDITION
.
So currently, it is impossible to prefix these function names with module's name, therefore creating potential naming conflicts:
ffc_condition_form_CONDITION
should actually be MODULE_ffc_condition_form_CONDITION
.
These two callbacks should probably also be implemented as hooks and I would guess a good place to start looking would be where they are called: see ffc.ffc_conditions_info.inc line 88 for form and ffc.module line 114 for execute.
This would allow external modules to implement MODULE_ffc_condition_form_CONDITION
and MODULE_ffc_condition_execute_CONDITION
.
I would greatly appreciate to have more feedbacks, comments, questions, objections, recommendations, suggestions, testing, reporting or concerns on any aspects of this ticket in general, I would be glad to provide more information or explain in further details.
Thanks to all in advance for your feedback, reviews, testing and reporting.
Cheers!