Cliff

Thanks for looking into this. I’ve had a bit more time today to look into this issue and I did find a work-around hack.

The problem seems to be some issue in the format of the initial conversion of EM6 Recurring Events to EM7 Repeating Events.

My solution is to go into each of these converted Repeating Events and temporarily change the recurrence range. If I move it back by a week and click update, the “Museum Hours: Thurs/Fri Fall Hours 10:00 am – 2:00 pm September 11, 2025 – December 21, 2025″ no longer shows up in the events_list scope=”today” shortcode output.

Then, all I have to do is set the recurrence range back to what it was, and the problem remains fixed. It’s not ideal, but it’s good to have a solution that isn’t too much work.

Thanks! That will work well.

As a follow up, is there any feature in this plugin that can display a message to a customer when they’re getting close to the threshold to get the free product? For instance, once they have over $100 in their cart, there’s a message saying “Just add $xx more to your cart to get a free gift”. Let me know if that’s possible with your plugin, or if it would have to be custom coded.

That’ll work. Thanks!

Thanks @ckadenge,

I ended up testing it out on a staging server with the Storefront theme and all plugins deactivated. It turns out that the culprit was a plugin called Semrush SEO Writing Assistant. I’ve posted the issue on that plugin’s support forum, and will leave it deactivated until there’s a fix.

That said, I do think it would be a nice feature to allow admins to be able to select whether or not they want Tour Kit tooltips to be active on their site or not.

Thanks again for your help!

Yes, the Divi Code module is et_pb_code. According to the Divi site, the Code module is intended for how I’m using it: “a blank canvas that allows you to add code to your page, such as plugin shortcodes or static HTML” (https://www.elegantthemes.com/documentation/divi/code/)

Functionally it seems very similar to the Gutenberg Custom HTML block. In both cases you can add HTML, shortcodes, and run some simple javascript/jQuery inside of <script> tags.

Does Relevanssi remove the Gutenberg Custom HTML block?

I’ll give the relevanssi_page_builder_shortcodes a try and see if that works.

Here’s what the the content looks like at the point of relevanssi_post_content_after_shortcodes:

(I output this to the using the error_log function. I’m redacting some content to keep the project private.)

[22-Jun-2022 05:09:23] WARNING: child 4377 said into stderr: "NOTICE: PHP message:       <p>With a mission to foster.</p>"
[22-Jun-2022 05:09:23] WARNING: child 4377 said into stderr: "<p>Embracing the collaboration. </p>             <h2>Want to Learn more?</h2>      "

There are two Divi Code modules each with a Pods shortcodes between the last </p> and the <h2> which aren’t showing up. But this is where the plot thickens because there’s also a hardcoded <h4> in those code modules which isn’t part of the Pods shortcode and that’s also not showing up.

Here’s what the code inside the Divi Code module looks like:

<h4>
  Committee Chair
</h4>
<div class="people-list">
[pods name="person" where="rel_committee_chair_of.post_title = 'Some Committee'" template="List of People - Committee Chairs"][/pods]
</div>

Seeing that the <h4>Committee Chair</h4> text didn’t show up in the indexing, it looks like the problem is actually with the Divi Code module and not the processing of the Pods shortcodes.

In fact I confirmed this by putting the Pods shortcode inside a Divi Text module, and when I did that, Relevanssi indexed it correctly.

So whatever Divi is doing with their Code module is preventing Relevanssi from seeing content in there. For my purposes, my problem is essentially solved. I don’t need to use the Code module to insert shortcodes; I can just change all of the shortcodes to use a Text module instead. But this is probably something you will want to look into to see if there is a way for Relevanssi to index content inside of the Divi Code module.

Thanks for your help in sorting this out. I wouldn’t have figured it out without the clues from the relevanssi_post_content_after_shortcodes function.

Thanks Brecht! I’ll try that out later this week and let you know if it works.