Humaniza
Forum Replies Created
-
Thanks a lot @nko for telling us you’ll look at this. π
Regards
It’s been more than a week since this issue was opened, and we haven’t received even a “looking at it” response from the developer. @nko Is this plugin still maintained?
I opened an issue on the Github source code management because we are not receiving answers here.
https://github.com/nk-crew/awb/issues/50Hi @nk,
Have you been able to take a look at this topic? Any day that passes the situation would be worse as iPhone users will increase IOS15 updates, affecting more visitors.Thank you,
Same here! After upgrading to IOS15 my boxes with mp4 background video stopped autoloading.
Strange, I made some tests and in mobile, if I turn the phone orientation, it shows.
On Safari Desktop, if I resize the window the video loads.
It’s like if the autoplay doesn’t by itself, and needs some kind of “resize event” or update in order to kick it.Please let me know if you find a solution.
- This reply was modified 4 years, 7 months ago by Humaniza.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] JavaScript ErrorOK I found it, so i will post the problem that was causing it:
It was related to the Google Analytics tracking code that was being printed by my template options.
As it was configured to be managed by Complianz, i suppose that when I hit the ACCEPT ALL button, it ran the equivalent code that made conflict with the legacy analytics code.
So I removed the analytics code from the theme options and the problem solved.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] JavaScript ErrorHi, same with only one of my sites (the rest are ok, but this one does):
https://www.totusfestum.com/It gives the error with both the “Enable JQuery migrate Helper” plugin active or inactive.
As soon as I press the “ACCEPT ALL” button of the popup, it launches the jQuery error that prevents the popup from closing:
Uncaught SyntaxError: unexpected token: identifier
jQuery 5
cmplzEnableStats https://www.totusfestum.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js?ver=4.9.6:1
jQuery 2
cmplzEnableStats https://www.totusfestum.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js?ver=4.9.6:1
cmplzFireCategories https://www.totusfestum.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js?ver=4.9.6:1
cmplzAcceptAllCookies https://www.totusfestum.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js?ver=4.9.6:1
<anonymous> https://www.totusfestum.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js?ver=4.9.6:1Hi,
Today we resolved this issue, and I wanted to post the solution here:Unexpectedly, it appeared to be related with an ssl problem in the configuration of the site.
I had seen some plugins giving this error:
Error: cURL error 35: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure (http_request_failed)
So that made some cURL calls to fail, hang…This was supposed to affect the cUrl call that wpscan does in order to get the information, so it halted there and made it break.
Last time I saw this error was in the WordPress health summary, telling me that it could not connect with that “SSL handshake” error.
The clue for me was that the Siteground plugin “SG Optimizer” failed when trying to enable ssl, telling that there was some ssl certificate error.
Finally with that error, I was able to open a ticket to SG support and they resolved it with the following diagnostic:”Regarding the WordPress Site Health and the error message and the cURL error 35, the Cloudflare DNS records were pointing in the DNS zone with us and that was caused the issue. The Cloudflare records were removed for the DNS zone with us and now the error isn’t showing up.”
After doing that, The WordPress health error dissapeared, and the WPSCAN plugin began to work fine!
So finally I can confirm it is resolved / working now for me, and I’m giving you the information I got so maybe it can be of help to anyone.
Thank you to the WPScan support crew, who really tried to resolve this, and to the Siteground support, that finally got the error and where able to give me a solution.
Forum: Plugins
In reply to: [Reviews and Rating β Google Reviews] Small style changeAfter updating and selected the Tiny theme, it’s all exactly as I wished. Thank for the support (and the mention in changelog ;P )
Forum: Plugins
In reply to: [Reviews and Rating β Google Reviews] Small style changeThank you for your amazing support. I tried your solution but the logo doesn’t show (I see on inspector that the style is correctly loaded but don’t know why the logo is hidden / not visible)
Also tried with a logo via absolute url, with the same result.
So, will wait for your new “tiny” theme.
Regards.Forum: Plugins
In reply to: [Reviews and Rating β Google Reviews] Small style changeAlso, how to change the word “reviews” after the review number?
Hi,
We currently have disabled your plugin on Production site but I have created a development clone (With Duplicator Pro), and have enabled your plugin there:
You can see yourself here:I’ve disabled too autooptimize and wpsupercache so that you don’t have to worry about cache issues.
You can try clicking on the different sections in the menu, and you will see that after doing scroll the sticky menu doesn’t work. If you see it work once, keep trying and it will stop working on another page or after refresh.For comparison, you can see production site, without your plugin, working fine:
I assure you that http://test.dev.humaniza.com/ is an exact clone of today’s production site, and the only differente is your plugin.
Hope this helps yo understand what can be the issue, looking forward to be able to use your plugin! Thank you
Hi @ethicalhack3r
Thatβs my own ip, which is odd as itβs imposible that I did 500 requests on my own, somehow something stuck and kept repeating like hanged.Iβm sorry I canβt give more clues.
@ethicalhack3r No, I only loaded the page, saw that it didn’t work and closed it. But it seems in fact, that it kept running and making resource consumption.
The plugin is now removed due to the advise they gave me so now I’m sure the plugin is now causing 0 more hits.@hristo-sg thanks for posting. Your help could be very valuable.
Could you (as you are from Siteground) simply create a test wordpress site within your server, install de wpscan plugin, activate it and see (as you would totally control the server, logs, environment) why it is failing?
I’m sure @ethicalhack3r could provide you with an api key for this test with no problem.Being us the testers, we are somehow blindfolded, as we no see any error, the plugin just hangs. But you could be able to see any task the plugin is doing, and maybe find what is preventing it from executing the vulnerabilities call.
Thank you.