Joe Dolson

Sounds like something that’s blocking the AJAX query to fetch the new pages; I might be able to tell more if you can provide a URL. But the first thing to try would be disabling all other plugins to see if it still happens then, and doing the same with your theme by switching to a default theme. That would help to isolate what might be causing the issue.

Testing this with a core theme, it rendered as expected. My guess is that something else is modifying the code before rendering; perhaps extra sanitizing in a plugin or your theme that’s breaking the code in the HTML block?

In order to do anything to help with this, I would need to at least have a link to your website.

Bluesky cards will only be supported in XPoster Pro, because I don’t plan to add support for image uploading to XPoster; but Twitter cards are based on meta data, and I can’t make any comments without a link to your site.

If the validator says that the cards are OK, then that’s what Twitter does to check the card, and they should show up. The fact that you need to add a parameter to get the link to load a card suggests that there’s something else going on on your site.

After following up with @jolo677 externally, I’ve resolved the issue and will be releasing an update soon.

That’s a screenshot of the regular calendar view, not the mini calendar. I don’t have enough context to tell anything more about it, though.

Where is this being displayed, and how is it added? Is it a shortcode? A widget?

That aria-labelledby attribute is only relevant when the event is being displayed in a modal; it won’t have any impact on accessibility in this context. However, I should probably ensure that the attribute isn’t output in the single view, since it will raise false positives in testing tools.

What I’d suggest is writing a small custom shortcode to render the script tag, instead of including it directly in the content. E.g.

add_shortcode( 'humix_embed', 'embed_humix_video' );
function embed_humix_video( $atts, $content ) {
	$args = shortcode_atts(
		array(
			'id'=> '',
		),
		$atts,
		'humix_embed'
	);

	$video_id = ( $args['id'] ) ? sanitize_text_field( $args['id'] ) : false;

	return ( $video_id ) ? '<script data-ezscrex="false" data-cfasync="false">(window.humixPlayers = window.humixPlayers || []).push({target: document.currentScript, videoID: ' . "'$video_id'" . '});</script><script async data-ezscrex="false" data-cfasync="false" src="https://www.humix.com/video.js"></script>' : '';
}

(untested.)

Generally speaking, a problem with HTTP resolution is going to be some kind of network problem, and is outside what I can control. Is this still happening?