Jay

Git itself is just a version control system, not really an interpreter. It’s basically a hard drive for storage ( to simplify it A LOT ).

By ‘add git hub libraries in WordPress’ I assume you found something need on Git that you want to use. You need to simply download it on GitHub, and move it where you want it to be ( the big green download button ).

Chances are you’ve probably not used git command line yet – if that’s the case, I suggest you start here: https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository

The best place to start is with adding a metabox. You can see the developer documentation here: https://developer.wordpress.org/reference/functions/add_meta_box/

Once you’re comfortable with that, or if you need something more simplistic, check this out: https://wordpress.org/plugins/cmb2/

Basically you need a metabox to actually accept the data, or your ‘customized values’. Once you have that, then, and only then should you be using save-post hook to update the meta data.

@burhansalt – Meta and Term queries are inherently slow. As your database grows, they will only slow down more.

Your query looks okay, so if I were you I would at minimum, cache the query results based on the arguments, either using Transients, or the Object Cache to prevent slamming your server every request.

https://codex.wordpress.org/Class_Reference/WP_Object_Cache

Simple solution – never modify core!!!

But in all honesty, you can report the bad plugin and someone will review it. https://wordpress.org/support/topic/reporting-bad-plugins?replies=7

Or if you’re on slack, just ask there. I’m not entirely sure it’s a ‘bad’ plugin, but it is definitely a user education issue, as Jan said.

With that being said though, consider writing a legitimate review for the plugin here: https://wordpress.org/support/view/plugin-reviews/hook-sniffer#postform

Too many times people forget that ratings actually impact a plugin’s performance, and we as devs learn from our mistakes. I’m not saying to flame the guy, but write an honest review about why this was a bad experience for you. It helps us devs so much!

Your answer is in your code.

<?php
wp_list_pages( array(
	'title_li' => '',
	'child_of' => '4721',
	'post_status' => 'publish' // remove draft
) );

Please do not post NSFW links on the forum. I have a link for that http://plugish.com/contact-me/

And no, it doesn’t look like it’s even activated. What theme are you using?

For the hook, I would recommend a cron-task. That way it’s ran once every say 15 minutes. A good place to start with crons is wp_schedule_event() https://codex.wordpress.org/Function_Reference/wp_schedule_event

The problem you’re going to have is the way you’re storing the dates mm/dd/yyyy while yes, it’s more readable for us Americans ( it’s how we do it ), it’s hard to compare the data directly in WP Query

You should update how you’re saving the meta data and force it to save in ISO-8601 format ( Y-m-d ) – though ultimately I always save date/timestamps as Unix format.

Otherwise, yes you’re forced to loop over every single post, then check the date via get_post_meta, and you would have to remove the meta_key and meta_value_num keys from the query I gave you.

There’s a filter for that, you can support multiple post types simply by dropping this code into your theme, or it’s own plugin if you wish.

<?php

function add_video_posts( $post_types ) {
	$post_types[] = "video_posts"; // Change this to the post type slug
	return $post_types;
}
add_filter( 'cwv3_post_types', 'add_video_posts' );

https://github.com/JayWood/content-warning-v3/wiki/Dev-Documentation#support-multiple-post-types