jeffreyscottfrench

If I’m remembering correctly: neither the plugin’s positioning method nor the standard positioning method of items in WordPress (using 1-15 or whatever it is) was accurate enough to insert the plugin exactly where I wanted it, so I manually called and placed it inside the block I needed via functions.php. CRP really is a pretty slick little plugin though, so thanks for all your work on it!

Ok, so after some research: CRP is being called manually from functions.php to ensure a very precise placement in the post-footer. This means that none of the CRP placement settings are being used/abided by in order to achieve this. This looks like its still the best option, and just hiding CRP with some javascript if it’s on a “Page.”

Hope this wasn’t keeping you up at night… Commenting the code better would’ve helped here – thanks for nothing, past me!

If you want to see it in this particular use (with some custom css), check https://blog.brettmatthews.com/

Its built on the genesis framework, and I’m not seeing anything in the child theme that would be altering the post_type at the first glance. CRP is looking on the page for a specific class in the body tag, or is querying the database?

I think I sourced the issue:

The echo_ald_crp function was being called manually from functions.php in the theme. This may have been because CRP is not (and likely was not at the time of theme authoring) displaying on “single-post” post types. CRP may have also had less placement options in the available settings at that time as well. Since the theme is a child theme of a framework, it may have been the decision that calling it in functions.php may have been cleaner in regards to ease of updating the child theme/parent theme set.

Was there a decision to make the default action be to not include CRP on single-post pages?

@ajay – I’ve tried this both on the page and via the settings page to exclude from Pages (type), and by ID number, and it still displays. Is this a known bug?

CRP v2.4.1
WP v4.9.4

Thanks!

I actually just dealt with a lot of repeating errors as well. It was because I had hard coded a call to an ad place by calling for its id. However I was not ready to serve ads via that place because none had been sold. So as a temp fix (which was wrong) I put that ad place in the trash, so it wouldn’t serve an empty ad and count towards views on that ad place.

Doing this created an error since the request found the ad, but it was in the trash, so it threw an error. Commented out the hardcoded request and no more errors.

That is a pretty slick plugin… thanks for the tip Fire Truck; worked like a charm!