-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
taxonomy hook with a filter #8
Comments
i will inspect my issue more after reading some docs |
this is to identiy the field in the form? When I created the plugin, I wasn't very consistent in my creation of filters. I would change this filter to:
which would allow a user to identify the form being submitted.
yes, that's quite possible, and hopefully can be improved in v5 |
please refer to #9 where i figured it all out. i think a filter should not only get an empty array but instead the possible estimated value instead |
Well, if multiple functions are hooked then you want the same value type to be passed, in this case an array.
in this case there is no estimated value, since the user opts for the filtered option (ie no form fields mapped here). |
I am going through the code and creating a Wiki Page on key functionality in processes handled by the plugin. |
in /includes/class-cf7-2-post-factory.php on line 1442 the true condition leads to adding an empty array instead of a filter function.
i think there should be
'cf7_2_post_filter-' . $this->post_properties['type'] . '-' . $field_to_map
instead of that empty array. Also the usage of$this->post_properties['type']
seems unconsistent sometimes with and somethimes without.The text was updated successfully, but these errors were encountered: