eamonlaser

Thanks for your reply. I tried after clearing the cache and it didn’t help. I then visited the page you suggested to post my question again, and saw one of your support team had posted that this was a known issue, and would be fixed in WooCommerce version 7.8.0 – the alert apparently appears even when sites aren’t using the WooCommercePayments plugin so is actually thought to be a WooCommerce Core issue.

Thank you for reaching out!

This is a known issue and should be fixed in WooCommerce version 7.8.0.

Here’s the PR for context: https://github.com/woocommerce/woocommerce/issues/36913

If you have access to the database, one workaround you can try is to locate the notice in one of these tables and change its status to “actioned.”

Thanks Patrick, I’m running a bulk Smush now and it appears to be working.

Thanks for your quick response – I wasn’t at my computer this weekend so didn’t see your answer until today. All seems to be working OK now.

I’ve just installed a test of Smush to see if how it works and I’m also getting this error message:

Error posting to API: cURL error 35: Unknown SSL protocol error in connection to smushpro.wpmudev.org:443

For a bit more information: On my site I’m not seeing this error for every image, because if I look in the media library I can see some images are saying that they’ve been smushed:

[Smush 10 images reduced by 21.6 KB (3.8%) Image size: 355.6 KB]

…while others are showing as “not processed”. If I click on the button to manually smush the image, I see the error message as above.

Hi Gregory,

I had to wait until a different website displayed the admin email confirmation screen and I have some screenshots which might help explain what I’m seeing.

Visit the (moved) login page as normal by going to
https://domain.com/secret/

Enter username and password and click: Log in

Site displays error:
Not Found
The requested URL /secret/ was not found on this server.

Refresh the page and alert displays:
Are you sure you want to send a form again?
To reopen this page Safari must resend a form. This might result in duplicate purchases, comments or other actions.

Click: Send

Then it displays the Administration email verification page
Administration email verification
Please verify that the administration email for this website is still correct.

Screengrabs of sequence when login page moved

I can’t recreate it, and I only mentioned it because a customer reported it to me as an error. Refreshing the page gets you through to the admin email verification page, so I’d always just put up with it.

I thought you might like to know.

The next time I see it I’ll take a screenshot.

You’re right, a mistype on my part when I posted this message. But still; I’ve used the Cerber login redirection function to change the standard login page and when I use that address (in my case it’s domain.com/secret/) and the admin verification page is triggered, I see the error I mentioned above.

• This reply was modified 3 years, 9 months ago by eamonlaser.

Different, but presumably related issue here. Latest posts widget cannot be saved. When trying to change “Number of Posts” from 4 posts to 5 posts results in the backend hanging, then this vague error message:

“There was an error. Could not update widget recent posts”

Then we have a long wait until the site is available again

If I disable the Gutenberg plugin (Version 9.8.1 in my case) I can immediately save edits to the latest news widget.

Thank you, I’ve installed the update and the plugin seems to be working OK.

I was getting upset because after replying to my first message it took several months to get any more information. Even saying “sorry, we’re still looking into it” would have suggested good customer service better than the radio silence I received.

My site felt very vulnerable not only because the plugin wasn’t working, but also because I didn’t seem to be getting any indication of work being done to fix the fault, or even confirmation that my messages were being received. I had started looking for alternatives.

Thank you very much for updating the plugin and fixing my problem.

I’ve also got the same problem. It was all working until a couple of weeks ago.

My email hosts asked me to try sending using localhost, port 25 and no authentication and that didn’t work. I’ve had to switch off SMTP Mailer plugin to get the forms to work.

Versions:
WordPress: 5.5.3
WordPress MS: No
PHP: 7.3.9-1+ubuntu16.04.1+deb.sury.org+1
WP Mail SMTP: 2.5.1

Params:
Mailer: smtp
Constants: Yes
ErrorInfo: SMTP connect() failed.
https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Host: smtp.interdns.co.uk
Port: 587
SMTPSecure: tls
SMTPAutoTLS: bool(true)
SMTPAuth: bool(true)

Server:
OpenSSL: OpenSSL 1.1.1c 28 May 2019

Debug:
Mailer: Other SMTP SMTP connect() failed.
https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting

SMTP Debug:
2020-11-20 14:44:03 Connection: opening to smtp.interdns.co.uk:587, timeout=300, options=array()
2020-11-20 14:44:03 Connection failed. Error #2:
stream_socket_client(): unable to connect to smtp.interdns.co.uk:587
(Connection refused)
[/home/spaceelevator/public_html/wp-includes/PHPMailer/SMTP.php line 344]
2020-11-20 14:44:03 SMTP ERROR: Failed to connect to server: Connection refused (111)
SMTP connect() failed.

Hi @gioni – do you have any clues yet what could be stopping my Cerber plugin from completing a scan?

I’ve been trying to get this resolved for 4 months!

Hi – it’s been 3 months since I first asked you about this, am I to assume that you don’t have an answer? Or don’t you want to help me resolve this issue?

I look after 50+ WordPress websites, and currently use iThemes Security (which is OK, but far from perfect) and I thought I would like to change all my websites to use Cerber as the interface is so much better, and I like the options it has.

I would happily pay for reliable, secure software that is maintained and supported, but I feel like you’re trying to ignore this problem hoping that I just go away!

Hi @lambdelivery – did you ever get this working? I’m stuck at the “Verify that your pixel is working correctly” stage of the setup. Facebook events manager just says “No activity yet”

I can see a couple of messages where people say they’ve had problems and then mysteriously the plugin started communicating with Facebook after a few hours. Is this just the way it works for everyone?

I’ve also uninstalled and reinstalled FB pixel plugin, and tried going back through the instructions several times. No activity recorded.

I’m using a WordPress hosted website, with PHP version 7.4

Hello – just wondering if you had any more ideas what to do to fix this?

I realised that somehow I’d supplied you with the wrong URL in my first post. The site is running at https://musicatstpeterswallingford.org.uk

By the way, I realised I hadn’t tried running the scan while using the standard WordPress 2020 theme, so I tried that today. I get the same error about the .htaccess file.

The file permissions for .htaccess are set to 644.
Is this correct?

Hi Gioni,

No, the quick scanner comes up with the same error:

[August 16, 2020, 3:22 pm][Scanner] Files: 2748

[August 16, 2020, 3:22 pm][Scanner] Parsing the list of files (step 5)

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

[August 16, 2020, 3:22 pm][Scanner] ERROR: Unable to open file /home/musicatstpeters/.htaccess

(this goes on for hours…!)