nswm

Hi Vytis

Thanks a lot for looking into this. It’s always annoying/frustrating when one is unable to replicate the problem. Not sure what else we can try.

Hi dshakya

It’s reassuring to hear it is not just our site with this issue. I wonder whether it is an issue with Google Charts API or Vizualizer per se. My guess is some sort of issue with a recent WordPress release or other plugin causing a conflict.

Super, Blaz.

I’ve updated and can confirm this has resolved the issue.

Thanks again for your help.

Great. Thanks. I’ve sent the whole .js file via your website.

Hi Blaz

I’ve not contacted Elegant Themes (Divi) yet but will do so. Can I email you as it may be easier if sending large files. I could attach the .js file in question maybe.

I have turned off all minify options in relation to JS I can see and purged the minified JS I think. The only reference to this text is now in the file wp-content/themes/Divi/js/custom.min.js. I guess this is a minified file given the ‘min’. Would the contents of this file be what you need or can I do something else somehow?

Hi Blaz

I’ve changed that code and it’s live on https://nswm.co.uk/insights/northstar-blog/do-you-suffer-from-money-tunnel-vision. The new id ‘rmp-voting-results’ shows but so too does the odd ‘1 2 3 4 5’ text still show.

Hi Blaz

Thanks again for looking into this. I appreciate the help and understand the limits of what you can provide, of course. As background, I use the Divi theme which is pretty popular. What I think I have found is some sort of conflict with the Javascript in the theme – specifically for the WooCommerce module (which I don’t use). I think this uses a rating system (for product reviews?)

I’m already in way over my head and don’t really understand much of this, but I used a string locator and tracked down this line in the theme JS and removed it:

window.et_pb_init_woo_star_rating=function($rating_selector){var $existing_stars=$rating_selector.closest("div").find("p.stars");0<$existing_stars.length&&$existing_stars.remove(),$rating_selector.hide().before('<p class="stars">\t\t\t\t<span>\t\t\t\t\t<a class="star-1" href="#">1</a>\t\t\t\t\t<a class="star-2" href="#">2</a>\t\t\t\t\t<a class="star-3" href="#">3</a>\t\t\t\t\t<a class="star-4" href="#">4</a>\t\t\t\t\t<a class="star-5" href="#">5</a>\t\t\t\t</span>\t\t\t</p>')}

Following the removal of this, the ratings shortcode seemed to work. My best guess is that there is some sort of variable (using a variant of ‘stars’?) that is shared between this and your plugin or something.

Do you think this sounds feasible and broadly right? If, so, I’ll contact the theme to try to figure out how I can remove this code from each theme updated.

I may be way off track here but need to get this nailed down before I add the ratings shortcode to all my posts.

I think your rating plugin is the best out there so really determined to get this working with my theme.

Thanks again.

That code again

<p class="stars">
<span>
<a class="star-1" href="#">1</a>
<a class="star-2" href="#">2</a>
<a class="star-3" href="#">3</a>
<a class="star-4" href="#">4</a>
<a class="star-5" href="#">5</a>
<span>
</p>

Hi again, Blaz.

Thanks for the quick responses. I tried disabling all plugins and removing all my custom CSS but the issue persists.

What is interesting is that when I enable ‘Add rating widget to all posts’, the ratings display correctly at the bottom of the page so it appears to be an issue with the shortcode only.

I’m no coder but I inspected the elements of both insertion methods to see if there were differences.

At the point in the code I think the {{avgrating}} variable is brought through, in the shortcode version code, it adds the lines:

<p class=”stars”>
<span>
1
2
3
4
5
<span>
</p>

These lines don’t appear to be present when inserted using the ‘Add rating widget to all posts’ method. The code then continues the same in both insertion methods.

Any ideas? Thanks again.

Hi. Yes, sorry I wasn’t clear. I’m using the shortcode [ratemypost].

In settings, if I leave “Custom results text” blank to use the default text, it displays:

“Average rating
1 2 3 4 5

/ 5. Ratings: 32”

(note line breaks and odd “1 2 3 4 5” text)

It also displays this odd text if I use the {{avgrating}} variable in the “Custom results text” field.

Hope that explains the issue a little clearer.

Hi Frank. Updated earlier today and it works. No more compatibility issue. Many thanks for fixing this.

Same issue here with Yoast (7.6) and Divi (3.5.1).

Yes, sg64. Exactly the same issue. Still liaising with the plugin developer but no resolution in the latest update it seems.

Hi Thomas.

Glad we are not the only ones with this issue.

This appears to have come about following the updates to QSM in early March.

I guess your issue is the same – we can’t access the Divi builder or other page elements like ‘screen options’ on any page with the QSM shortcode.

I raised this via email ([email protected]) a few weeks ago and was told they were looking into it. Not heard anything yet.

I will post here if I get any sort of resolution.

I’m also getting this error. I have now temporarily renamed the Project Panorama plugin folder as it seemed to crash my site. Hope this can get resolved.