jstubbs034
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Plugin Version 7.2 ErrorsRight now we are using 7.0.1 and I don’tplan on updating it because our site is live and everytime I update the plugin it ruins our website pagespeed. I may reclone the site later today and update the plugin but that is the best I can offer to you for a report.
Forum: Plugins
In reply to: [LiteSpeed Cache] Plugin Version 7.2 ErrorsAlso if it is normal for it to be displaying that error when coming out of the Elementor page builder how come it doesn’t do it when 7.1, 7.0.1 or 6.5.4 is installed? Also how come 7.2 is the only version having REST API issues with QUIC.cloud and disconnecting the CDN none of the other versions do that.
Forum: Plugins
In reply to: [LiteSpeed Cache] Plugin Version 7.2 ErrorsI get the Elementor error however that still doesn’t explain the disconnect from QUIC.cloud just from upgrading the plugin from 7.1 to 7.2 it also doesn’t explain the pagespeed drop which is actually pretty harsh or the random REST API errors that pop up in the WordPress dashboard saying that the plugin cannot connect to QUIC.cloud. None of those issues exist when the plugin is set back to 7.1, 7.0.1, or even 6.5.4. 7.2 Has given so many problems after udating it that I’m forced to run my site on an outdated version just to keep the connection to QUIC.cloud. On another clients website that was updated to 7.2 their pagespeed score for desktop fell from a 99 to an 83 and it too disconnected from QUIC.cloud on updating the plugin and had to be reconnected and after reconnecting it the pagespeed dropped as mentioned. If I restore it back to 7.1 the pagespeed score goes back upp to 99 on desktop. So something is off with that plugin.
Forum: Plugins
In reply to: [LiteSpeed Cache] The setting Disable All Features is currently enabled.@litetim Here you go https://ww.wp.xz.cn/support/topic/plugin-version-7-2-errors/
- This reply was modified 11 months ago by jstubbs034.
- This reply was modified 11 months ago by jstubbs034.
Forum: Plugins
In reply to: [LiteSpeed Cache] The setting Disable All Features is currently enabled.I’ve been getting this problem myself after updating the plugin to 7.2. If I rollback to 7.1 it is fine no issues, update to version 7.2 and all I ever get after editing a page with elementor is this error at the top The setting Disable All Features is currently enabled. Click here to change.
It doesn’t make any sense and pretty sure it’s messing with our connection to QUIC.cloud too because our pagespeed drops horribly. If I roll back to 7.1 or even 6.5.4 the pagespeed goes up to normal and no errors.
I even cloned our site to a staging site and disabled all plugins except for elementor and even reverted to a default theme same issue in 7.2 The setting Disable All Features is currently enabled. Click here to change.
So something is terribly wrong with the plugin on 7.2 version it’s not an issue with people’s websites. The plugin is malfunctioning and pretty badly. I will rollback to 6.5.4 because who knows when the problems started happening in version 7. The fact it completely disengages websites from QUIC.cloud is crazy and even though no debug features are turned on with it claiming they are is a serious problem across the board.
We updated the server LiteSpeed version to 6.3.3 hoping that would resolve the problem, but nope same issue in 7.2 with the debug error and multiple REST API errors being displayed randomly at times. None of these issues happen on 7.1 or 6.5.4 ONLY in version 7.2.
You guys need to take a look at the plugin and maybe QC it before releasing updates that cause major perfomance problems on websites because that impacts ranking, as well.
Example on version 7.2 our pagespeed score drops to a 47 on desktop and a 37 in mobile. On version 6.5.4 our pagespeed score is a 95 on desktop and a 89 on mobile. That’s a huge difference and as mentioned above I tested this on a clone staging site of our website and it didn’t matter what theme was used or what plugins were disabled the same error all the time setting Disable All Features is currently enabled. Click here to change.
The only plugin I didn’t disable was elementor page builder but if I disabled that then we’d have no page structure so either your plugin version 7.2 has a serious issue with the elementor page builder or it has a serious issue altogether.
- This reply was modified 11 months, 1 week ago by jstubbs034.
Forum: Reviews
In reply to: [SEOPress - AI SEO Plugin & On-site SEO] Very DisappointedI checked all the settings never saw anything like that but no worries Microsoft has there own plugin for Clarity so problem solved.
Forum: Reviews
In reply to: [SEOPress - AI SEO Plugin & On-site SEO] Very DisappointedWell, I don’t believe it was a crawler issue as to why your plugin couldn’t see content on the page for a keyword used. Google Bot and other bots crawl our website just fine. Again, your plugin is supposed to be compatible to Elementor which means it ought to be able to see the page content right? Even canonical URL’s it couldn’t identify after they were set. It couldn’t detect open graph items that where setup right inside of itself. A plugin displaying that kind of behavior wouldn’t present any benefit to a website for SEO. Also where was the settings to configure Mircosoft Clarity? I went through the plugin I had and I never saw anything to connect a Mircosoft Clarity account with your plugin which is something you advertised as being included. Again, in the version of your plugin I was using it was clear no option for connecting any clarity account with it.
Forum: Reviews
In reply to: [SEOPress - AI SEO Plugin & On-site SEO] Very DisappointedHi, you wouldn’t be able to run anthing on our site as we use a strong firewall so unless you have permission you wouldn’t do anything but get yourself auto banned by the firewall trying to probe. Also, if you had read the full review I left you woud see where I mentioned that the plugin was uninstalled and replaced with one that worked with zero issues. You guys might be onto something with your plugin but I don’t feel your plugin is quite ready for some WordPress websites that might be more complex using Elementor. We never had a single issue once we installed Rank Math it just worked flawlessly where your plugin couldn’t even detect keywords that were placed in the content at the proper ratio. Rank Math picked it right up where your plugin kept saying the keyword used wasn’t in the content. That was on top of all the other issues outlined in my initial review. With that said, we have no plans of using your plugin moving forward as our website is stable and already has been launched. Thanks anyway.
No, I didn’t read that post I just ran the PHP compatibility checker and it referenced your plugin as one that wasn’t compatible with PHP version 7.
Either way, it doesn’t much matter at this point the client’s host doesn’t support IPv6 in their current PHP 5.6 config and my client’s website isn’t ready for PHP version 7 as they have other plugins that aren’t compatible with 7. That and the warning messages that your plugin was spitting out made them very unhappy.
They requested that wordfence be reinstalled so that is what I had to do to satisfy them. If it hadn’t been for those warning messages being blasted on the front end they most likely would have kept the plugin.
Ok so I checked with Site Ground this morning and they told me that the PHP version 5.6 they run doesn’t have IPv6 support only IPv4 support. They said PHP version 7.0 has IPv6 support but, after running a PHP compatibility check on the client’s website your plugin isn’t compatible with PHP version 7 so not sure if I should return them back to the security plugin they had before which was WordFence or not.
Hi and thanks for the reply.
It’s not my server it’s the client’s server and they are with SiteGround so I’m not sure which version of PHP the server is using. I have passed the information along to my client so they can contact SiteGround and check on the PHP version being used.
SiteGround isn’t my first choice for hosting but, the client already had this WordPress site and hosting setup when I picked them up.
Anyway, I’ll keep you posted on what they reply back with concerning the PHP version.
You have to clear your browser cache in order to see the no right click copyright protection working. If you just enable it and then go out to the front end it will appear to not be working until you clear your browser cache.