The save_fields_for_post() method in the post context has a guard condition where it checks the post ID before saving data to it. This is for the situation where another post gets updated when a post is saved and prevents meta data being saved to another post. Ref:
|
// Make sure this hook fired on the post being saved, not a side-effect post for which the $_POST context is invalid. |
This was introduced in #147.
There is no such protection for terms. If a term gets saved and some code updates another term, Fieldmanager will write its term meta to that term too. Ref:
|
public function save_term_fields( $term_id, $tt_id, $taxonomy ) { |
The
save_fields_for_post()method in the post context has a guard condition where it checks the post ID before saving data to it. This is for the situation where another post gets updated when a post is saved and prevents meta data being saved to another post. Ref:wordpress-fieldmanager/php/context/class-fieldmanager-context-post.php
Line 185 in 6e46daf
This was introduced in #147.
There is no such protection for terms. If a term gets saved and some code updates another term, Fieldmanager will write its term meta to that term too. Ref:
wordpress-fieldmanager/php/context/class-fieldmanager-context-term.php
Line 284 in 6e46daf