vavroom

I’ve opened an issue on the project’s GitHub.

I hope the developers will be responsive and that a solution comes quickly.

https://github.com/Automattic/sensei/issues/4129

Thanks again @cena

I’m already having to seriously hack Sensei as it is to render WCAG 2.1 markup. This is what I deem “passive inaccessibility”. But actively blocking code that would allow using more accessible features… That’s even more sad ??

I think I’ll end up relying on custom fields for this to give more control as to how content is presented.

Thank you @cena I appreciate the answer, though I can’t say the answer makes me happy.

I’ve looked at the GitHub issue linked, and the ones linked from that. It is unclear which patch you are suggesting I try – especially since the PRs are either closed or have discussion that leads to lack of clarity.

This is a significant concern, one that adds itself to the already long list of accessibility concerns that Sensei LMS faces.

There is an increasing move towards online education, and the fact that online education is often the ONLY education available, and the fact that education must be accessible for all. Vimeo and YouTube do not allow for custom captions, video description, timed transcripts, or chapters. There are video player solutions that do allow this. Able Player is one such solution. Able player relies on pretty straight forward markup.

By forcing the sanitizing of tags to limit to a few things Sensei LMS deems acceptable, you are forcing people to be unable to provide accessible videos.

Thanks @gabrielfuentes

FWIW, when you follow the link to the plugin homepage from the installed plugin, it leads you to the WooCommerce site, and from there when you are looking for support, this is where you end up.

I’ll go repost my question in the more appropriate forum. But it’d be nice if the makers of Sensei LMS (e.g. WooCommerce) made it an easier workflow to get to the right place.

Hi Rajesh,

The only info I get in the console are the ones I quoted in my original post.

Ah ha! Using another plugin, Custom Post Type, the option to make the editor box disappear becomes available.

Thank you ??

Thank you Ricky! Haven’t used your solution, but I found my answer in the solution!

I had used query_posts to run a couple loops, but posts weren’t restricted to the actual tag. The addition of “$query_string.” resolved that!

Thank you.

For future reference, here’s what I’ve done in the end:

query_posts($query_string.'&cat=17');
				echo '<h2>Cats</h2>';
	while (have_posts()) : the_post();
		?><h3><?php the_title(); ?></h3>
		<?php the_excerpt();
		endwhile;
		wp_reset_query(); 

	query_posts($query_string.'&cat=16');
				echo '<h2>Dogs</h2>';
	while (have_posts()) : the_post();
		?><h3><?php the_title(); ?></h3>
		<?php the_excerpt();
		endwhile;

No idea? Anyone?

With the assistance of a couple people, finally got this working.

Instead of calling the custom field like so:
echo get_post_meta($post->ID, 'recipe', true);

I am doing this:

$nsval = get_post_meta($post->ID, 'recipe', true);
$nsoutput = do_shortcode( $nsval ) ;
print $nsoutput;

I know it’s frowned upon to bump a topic, but I could REALLY use some help on this and I’m no closer to figuring it out, despite continued testing of various ways to accomplish this… Anyone?

Thanks

Looks like no one has any ideas here.

Surely someone’s run into this issue before?

Ah ha! I’ve done it now ?? It hadn’t occured to me to use category tags on a tag.php. But playing around a bit, that’s what I’m doing. All the ones that I want to single out belong to a specific category already.

Sooo, here’s what I’m doing inside the loop:

<?php if ( in_category('3') ): ?>
  something
<?php   else : ?>
something else
<?php endif; ?>

Using the assigned category avoids having an hyper-long array, and means I don’t have to edit the tag.php all the time I add new stuff ??

Thanks to all who helped ??

Otto, thanks for that. I’ll try it.

What do you mean by “start the Loop early” ?

Thanks

Thanks bekabug, I might have to resort to something like this, yes.

I was hoping to avoid that approach, because at last count I have over 150 tags, and it’ll grow, too… So it will make for a rather long conditional statement.

Sorry, no suggestion for you. I’ve had similar problem. Post up for nearly two weeks, no one made suggestion that worked…