bobjones

Thanks, Jesse.

The plugin finally deactivated after I selected the link and waited 15 minutes or so. I presume the dashboard would have loaded eventually if I had waited long enough.

However, waiting time for any plugin link should only be a few seconds. I’d like to use Total Upkeep, but I don’t see how if it behaves so sluggishly.

Thanks for the link, Stef.

The author’s function appears similar to the one provided by JetPack at Animesh’s link (https://jetpack.com/support/related-posts/customize-related-posts/#disable).

This function is not ideal, as it blocks JP Related Posts in both the post and the content block that appears within the post, but at least related posts are not appearing in the content block.

Thanks to all for the recommendations!

• This reply was modified 3 years, 9 months ago by bobjones.

Animesh:

Again, I want to block JP Related Posts for Content Block custom post types, not for WordPress posts. The Jetpack function to disable Related Posts for specific WordPress posts would not apply.

Just for the heck of it, I used the Jetpack function to disable Related Posts with an individual content block id, but that had no effect.

Thanks, Johan.

I’m finding now that my css fix disables JetPack Related Posts in the content block and in the WordPress post that contains the content block.

This is not ideal, but still the most workable solution.

Here’s a link to the thread I created in the JetPack forum, in case you choose to investigate further during future development:

https://www.ads-software.com/support/topic/disabling-jetpack-related-posts-for-custom-post-types/#post-14517633

Thanks for your reply, Animesh.

You correctly inferred that I’m using a plugin called Content Blocks (Custom Post Widget) to insert content blocks in my WordPress posts.

Unfortunately, the function you provided has no effect when I add it to the plugin and crashes my site when I add it to my theme’s functions.php.

JP Related Posts continue to appear in my content block and not on the post.

I’m able to hide JP Related Posts (and JP Likes, for that matter) with CSS. Oddly, this hides related posts for the entire page, although I’ve targeted only the Content Blocks div. But at least related posts aren’t showing up in the content block.

The Hide Jetpack Likes css works as intended, hiding JP Likes in the content block only.

/* Hide Jetpack Related Posts for Content Blocks  */
div.content_block .jp-relatedposts {
	display: none !important;
}

/* Hide Jetpack Likes for Content Blocks  */
div.content_block .jetpack-likes-widget-wrapper {
	display: none;}

• This reply was modified 3 years, 9 months ago by bobjones.

I’m not sure where those content filters would be in Jetpack, but it sounds like that would disable related posts everywhere.

This css ultimately worked for me:

div.content_block #jp-relatedposts {
	display: none !important;
}

I could use some help here.

What CSS should I be seeing for normal dropdown behavior?

Right now I see class="wprmenu_parent_item" for the parent and <ul class="sub-menu" style="display: none;">for the submenu item.

Naturally, the submenu should not display until the user invokes the parent. At that point, the arrow turns down and the submenu opens. But that isn’t happening now.

I’ve commented out all the CSS for my theme’s submenus to prevent any conflict.

So, again, what CSS should I be looking for?

Is anyone supporting this plugin?

Thank you.

• This reply was modified 3 years, 11 months ago by bobjones.
• This reply was modified 3 years, 11 months ago by bobjones.

I won’t be able to stage the site, Frank, but appreciate your attention to this issue.

I’ll just check “Leave as is”, since that works best.

With “combine and link deferred in head”, the problem remains when the site is fully loaded, and I see a lot of undesired fonts.

If you have the time available and would like to contact me privately, I’ll be happy to provide a real-time demonstration!

FranK:

Sent you a note via your site’s contact form.

How about this?

<link rel="stylesheet" media="print" onload="this.onload=null;this.media='all';" id="ao_optimized_gfonts" href="https://fonts.googleapis.com/css?family=Open+Sans%3A400italic%2C400%2C600%2C700%7CRoboto+Slab%3A400%2C300%2C700&display=swap" />

Frank, I know how to “show source” from the developer tools, but I see no way to share a url from the source.

However, I can capture the source content of the home page with “Combine and link deferred in head” enabled, and share it with you privately, if that would be of any help.

Again, I point out a specific issue, and you deflect with requests for screenshots and page links, which I cannot provide because this is a localhost test site.

If you’re not going to support your theme on this forum, I’m outta here.

I believe I clearly laid out the problem and requested a particular action.

If all you can do is deflect a request for support, then I’ll look elsewhere for a WordPress theme.

Didn’t work at all for me either. When I tried to import the xml file output by WPS Menu Exporter, all WordPress did was list the names of several pages and indicate the pages “already exist”.

Useless.