Chris J. Zähller
Forum Replies Created
-
Forum: Plugins
In reply to: [Five-Star Ratings Shortcode] A warningActually, I know the cause of this warning. The Freemius SDK used to manage the PRO version of the plugin had a zero-day vulnerability which has since been patched. The current version of the Five Star Ratings Shortcode plugin uses the patched version.
As long as you update to v1.2.39 or later you should be safe.
Forum: Plugins
In reply to: [Five-Star Ratings Shortcode] A warning@jmd87fr Sorry it took so long to reply; I just saw this. Can you please post a link to the source of this information? FWIW, the current version of the plugin is 1.2.41. You should update ASAP.
See https://plugintests.com/plugins/wporg/five-star-ratings-shortcode/latest
Forum: Plugins
In reply to: [Five-Star Ratings Shortcode] New Shortodes Don’t Work@b3ndoyle Did you resolve this?
Forum: Plugins
In reply to: [Five-Star Ratings Shortcode] New Shortodes Don’t WorkAlso, I noticed you are hiding the numeric output and substituting your own. You don’t have to do that. For the first review on this page (https://www.petcheckers.co.uk/best-non-clumping-cat-litter/) just enter [rating stars=”4.1″] and it will output 4.1. If you look at the source code, there’s a screen reader text — and since you used [rating stars=”4.0″] it doesn’t agree with your displayed rating.
Forum: Plugins
In reply to: [Five-Star Ratings Shortcode] New Shortodes Don’t WorkHi, I tried to look at the post, but it’s 404 not found.
Please open developer tools and look at the console to see if there are any errors related to the plugin.
Check for plugin conflicts — there might be a plugin active on this post that is not active on other posts. Also check the template — if it’s a different template from you other posts, it may contain conflicting code.
Try deleting the post and recreating it as a new post.
BTW your cookies plugin is also throwing errors. It’s possible that when that error occurs it stops JavaScript execution including the JS from Five Star Ratings Shortcode.
Keep me posted.
- This reply was modified 3 years, 11 months ago by Chris J. Zähller.
🤘Thanks!
I’m on an OpenLiteSpeed server. The LSCache plugin is optimized for it. Adding another cache plugin would just complicate matters.
I wound up adding this to .htaccess and it seems to have solved it for now:
<IfModule LiteSpeed> RewriteEngine on CacheLookup on RewriteRule .* - [E=Cache-Vary:wp-postpass] </IfModule LiteSpeed>Forum: Plugins
In reply to: [WPSSO Core - Complete Schema Markup and Meta Tags] Turn Off NotificationsThanks! I’ll look into that.
Forum: Plugins
In reply to: [WPSSO Core - Complete Schema Markup and Meta Tags] Turn Off NotificationsBetween Cloudflare caching and the Openlitespeed cache plugin and setting very long “expires” headers, it’s nearly always a caching issue.
Forum: Plugins
In reply to: [WPSSO Core - Complete Schema Markup and Meta Tags] Turn Off NotificationsEDIT: it was a caching issue.
The notices I’m seeing with no means to dismiss are not errors that must be fixed. For instance, this update notice won’t go away and can’t be dismissed. Refreshing the page or navigating to a different page has no effect.
It’s possible that it’s a caching issue. I will look into that.
- This reply was modified 4 years, 2 months ago by Chris J. Zähller.
Forum: Plugins
In reply to: [WPSSO Core - Complete Schema Markup and Meta Tags] Turn Off NotificationsThere’s no “dismiss” link in the messages. Seems to have gone missing in a recent update.
Forum: Plugins
In reply to: [wp-Typography] Deprecated PHP (not compatible with PHP 8)Thanks for keeping me updated on this.
Forum: Plugins
In reply to: [wp-Typography] Deprecated PHP (not compatible with PHP 8)Thanks. Leaving this open but as of now, it’s not really a support request — more of an open issue. No need to reply except to mark the fix has happened.
I think it was a caching error. Probably your script was loading before jQuery. Everything seems to work now.
Forum: Plugins
In reply to: [wp-Typography] Deprecated PHP (not compatible with PHP 8)I traced the fatal error to a PHP typo in my functions.php, so the plugin is not at fault. Nonetheless it does log a deprecation error for PHP8, which is not trivial. I’m not yet marking this closed for that reason.