Edit Invalid Answer The answer below is invalid as get_the_id() and get_the_ID() both return the required ID of the post inside the Loop. Thanks to @Jess_Pinkman for pointing it out. Your code should be working fine, but the only issue is you are using an incorrect function to get the ID of the post inside … Read more
you can make repeating fields with the WP alchemy class http://www.farinspace.com/wpalchemy-metabox/#have_fields_and_multi
Probably your already solved this (hopefully not by hand). This part of your question is intriguing: I found that if I open a post through WordPress front-end and then click “update” the custom field data and the post content “sync” Do you mean back-end, right? If so, I think a bulk update would solve this … Read more
As others figured already out: If you have third party plugins with custom queries, you’ll have a bad day! One solution might be caching your results. Template (e.g.: page.php) while (have_posts()): the_post(); global $my_cached_data; $post_id = get_the_ID(); /* * If you have single meta keys, this array_map function * makes them easy to access; otherwise … Read more
The meta value is read when the block loads and assigned to the block attribute. Changes to the block will update the attribute and when the post saves the value will save to the meta. So, as far as I understood, there is no need to actually save anything in the registerBlockType js function. The … Read more
So based on our discussion, the meta named opposition (for match posts) has its value set to the slug of the corresponding club post; e.g. club-1, club-two, etc., right? If so, then you first get the ID of the club post using a custom query (see in the code below) and then you can access … Read more
This will do. The slug is saved on the wp_posts while custom fields are on the wp_posts_meta. If you want to make it like that you can use an action hook on save_post that will get the value of the custom fields and saves it as the post slug. Here is the code add_action(‘save_post’, ‘set_slug’); … Read more
I figured I’ll leave the meta values saving on multiple fields in the db, because I’ve been doing allot of pre_get_post query filtering. Some of the features in there are for searching/filtering on post meta data and would it start making things very difficult if I was to start saving values into doubly serialized values. … Read more
Through a lot more research and some trial and error, I figured out the correct code to use that will restrict a post from being edited based on the user ID AND a custom meta field. $user = get_current_user_id(); $super_users = array(1); The first two pieces of code within the function are important for restricting … Read more
“You should not write to the DB on front end requests” is the eleventh commandment. Your performance will deteriorate due to the writes locking down the table much more than the impact the size of the table will have. You should probably write such data in files instead of DB, or at least use a … Read more