Criss Swaim

You are correct in the tag option will pull posts by tags.

try this->r[‘tags’] to retrieve the tag value

BUT….since this bit of custom code will be lost if you upgrade the plugin, be careful. Also, using the tag option may have other impacts. What you might try is to pass in an option like header=’venice’, which appends the option to the end of the plugin options array and then access as this->r[‘header’]

Of course none of this is supported, but post your results back here as it may be helpful to others.

From my comment above:

By putting the css in the custom css file in your template,
the changes will not be lost with upgrades to the plugin.
And if you are using a child template, upgrades to the
template will not affect the custom css which is in
the child theme folder.

If you follow the guidelines in the doc for custom styling, the only time you need to be concerned with loosing the css changes is when you upgrade the theme. Or if you use a child theme, only when you upgrade the child theme. An additional reason for using child themes.

If you change the plugin css directly, then the changes will be lost, so don’t do that. Set up a custom css file.

It seems that the solution provided by msubretort which uses css to hide the YARRP is the quickest way forward at this point. This technique could also be applied to QuickAdsense and any other post plugin.

Use custom css (see doc for placement location) and then provide the specific tag to hide, starting with the tpg division. Use a browser debugger to find the exact sequence of tags to hide so only those YARRP classes in the tpg-get-post div are hidden.

By putting the css in the custom css file in your template, the changes will not be lost with upgrades to the plugin. And if you are using a child template, upgrades to the template will not affect the custom css which is in the child theme folder.

What the plugin should do is accurately display the post on a static page. Then allow you to customize display options.

The other option is with the premium version you can call a custom function and turn off/on the hooks for the post. While the plugin supports that capability, it is up to the developer to write the code. I am unable to support custome php solutions, but here is what my testing code looked like (with echo’s for testing included)

function tpg_gp_pst_post_filter($content,$cfp=null) {
	/*
	 * the following code is a sample to add the MPR & Yet Another Related post plugins
	 * uncomment to activate sample
	*/
	echo "in pst_post filter<br>";
    add_filter('the_content','MRP_auto_related_posts');
    global $yarpp;
    add_filter('the_content', array($yarpp,'the_content'), 1200);
	return $content;
}

/**
 *	tpg_gp_pre_plugin_filter
 *
 * allow custom function to be invoke before content
 *
 * @param	string	content
 * @param	string	custom function parm
 * @return	string  content
 *
 */
function tpg_gp_pre_plugin_filter($content,$cfp=null) {
	/*
	 * the following code is a sampe to turn off MPR & Yet Another Related post plugins
	 * uncomment to activate sample
	*/
	echo "in pre_plugin filter<br>";
    remove_filter('the_content','MRP_auto_related_posts');
    global $yarpp;
    remove_filter('the_content', array($yarpp,'the_content'), 1200);
	return $content;
}

Yes, the shorten_content feature is risky as it either counts characters or words (defined by space separation) and trims the content when the limit is reached. It is not aware of html tags. It should only be be used when control over content is very controlled. Using the read-more tag is safer.

I will update the doc to reflect this restriction.

I believe your cat name slug is swelling-and-water-retention. Caps are important! I think the wp query uses the slug and not the description.

I have not tried to prevent the style sheet from loading, so this is untested. If the wp_deregister_style is not working you might try

<?php wp_dequeue_style( ‘tpg_get_posts_css’ ) ?>

MCM – If your are still monitoring this, I looked at the plugin and realized that it will pull custom posts

use the parm post_type=”myCustomPost”

Undocumented feature…..

The published date is only shown on the byline. Your code is only displaying the title. At this time the plugin does not permit customizing the title line.