1waytoheaven

My guess is, he wants to reduce the bulk of his images, and is not worried about the few browsers that don’t handle WebP.

@ethanchoi

Almost a month ago, the 1.6.4.1 update began breaking many sites for various reasons, ours included.

The reason is plain if you check the WP Admin plugin pane for WPForms Lite. The update has NOT been tested with the latest WP!

To expect users to debug your plugin for you on their live sites is not acceptable, particularly when the developers have not even bothered to ensure their update is compatible with WP.

I have made a screen shot to illustrate the Warning users see, but I find no way to upload it to this thread. However, you will see it yourself if you update to the latest WP version, then view the WPForms Lite plugin update pane.

The plugin’s own interface, when logged into WP Admin declares the warning:

WARNING: This plugin has not been tested with your current version of WordPress.

I have the latest WP, and all my other plugins are up to date.

When I reported this to WPForms, last year, they said they are investigating, but then locked such threads without resolving the bug.

We have to revert to WPForms 1.6.4 or switch to a more reliable Forms plugin.

It should be easy to fix, since WP shows the code-line error, but the plugin owners can’t be bothered fixing it.

Mezloh, Yes this is a very common problem with this plugin, many users have reported similar problems since WPForms Lite was updated to 1.6.4.1.

Indeed, the plugin’s own interface, when logged into WP Admin declares the warning:

WARNING: This plugin has not been tested with your current version of WordPress.

Like you I have the latest WP, and all my other plugins are up to date.

When I reported this to WPForms, last year, they said they are investigating, but then locked such threads without resolving the bug.

Like us, you’ll have to revert to WPForms 1.6.4 or switch to a more reliable Forms plugin.

It should be easy to fix, since WP shows the code line error, but the plugin owners can’t be bothered fixing it.

Shame eh?

I confirm I also have the same error, using Litespeed cache ona Lightspeed server.

I reverted to the WPFormsLite 1.6.4 that didn’t break our site.

Will this be fixed this year, or do we have to run the old version 1.6.4 until next year?

A further thought to help track it down…

On the next WP Mail SMTP update, insist that the password is inserted in the wp_config.php file, instead of having it in the WP Admin pane.

Don’t make it optional anymore; and then you’ll wake those asleep at the wheel, cause them to report it, and make the plugin even more secure at the same time.

Only a suggestion, not a criticism.:)

Colin

Dear Gregor,

Not to fuss, it’s not crucial ??

If this would be a plugin issue, we would be able to reproduce it and a lot of other users would be reporting it.

It may be a clash with the particular set of plugins I use, on a Lightspeed server, so you’d have to test with a wide range of set-ups before being able to reproduce it.

I very much doubt many punters would be bothered to report minor bugs to plugin developers, much more likely to shrug, and either delete the plugin, or put up with the bug. It takes quite an effort to report a bug, and as you well know, even more to track it down.

Perhaps this thread will nudge more users to check their WP Mail SMTP security settings, and attempt to hide them from the vulnerable WP Admin panel.

We will see ??

Thank you again.

Colin

Dear Gregor,

Yes, I know the feeling.

My response is to leave it a day or two, and then the solution falls on my head from a tree.

However, in compassion, I did trouble my host, who looked at this thread, and responded…

Q/
Hello,

There’s nothing on our end that would be blocking custom options from being set. Our system doesn’t have anything special going on for WordPress.

Best Regards,

Management
/Q

Ergo… either my fingers are fatter than I think they are or the plugin needs polishing.

Colin

Dear Gregor,

I appreciate the trouble you are taking to fix this.

As you asked, I copied and pasted this…

define( 'WPMS_ON', true );
define( 'WPMS_SMTP_PASS', 'Mypwdishere' );

… in the correct wp_config.php file, uploaded by sFTP as usual, purged all my Litespeed caches, refreshed my browser cache, and sadly… no change.
Nothing “greyed out” pwd still accessible in the WP Mail SMTP settings pane.

I’m not keen on troubling my host about it, to be frank, because they are excellent, and would not be doing anything on my site set-up that I’d not be informed about beforehand.

Let’s just leave it be for now, I’ve taken too much of your time already.

Thank you ??

Colin

Thank you Gregor,

1) Yes, I confirm I’m editing the WP root wp-config.php file, and placing the code in the correct location.

All my other edits to the root wp-config file work as expected.

2) No, nothing is greyed out in the WP Mail SMTP settings pane.

I won’t be the only user unable to get this functioning.

I’m on a Lightspeed server, in case that is relevant.

Another straw to clutch at; I have the WP files in a folder, not the domain root, but they are in the “WP root”.

ie. https://www.mydomain/My_WP_Folder/

Colin

That’s precisely why I posted a review, and glad you are paying attention.

Please test thoroughly BEFORE dumping another update on us all ??

This forum software introduced the wrong character (pobably because I didn’t use the BB formatting, like you did.)

In my original live code I did indeed use the correct apostrophe, not the artefact introduced here.

So, nice spot, but no change at my end.

Something is still not right.

Colin