WaldenPondDesign

I suspect it’s an issue with Plesk Obsidian 18.0, I migrated the site to an older server running Plesk Onyx 17.x and it ran correctly. I suspect you will have more issues as more people start using the latest version of Plesk. Let me know if you need more info from me.

Slava,

I fixed the initial quote, still having same problem.

/* old setup */
/*define( ‘WPMS_ON’, true ); */
/*define( ‘WPMS_SMTP_PASS’, “XXXXXXXXXX” ); */

define( ‘WPMS_ON’, true );
define( ‘WPMS_SMTP_PASS’, “XXXXXXXXXX” );

Below is the error message. Note we are hiding the password in wp-config.php file. Contents are listed below. Note this is line 88 and 89 as mentioned in the second log entry

define( ‘WPMS_ON’, true );
define( ‘WPMS_SMTP_PASS’, “XXXXXXXXXXX” );

[Mon Dec 16 16:41:59.667690 2019] [fcgid:warn] [pid 29791:tid 139898124220160] [client 98.217.169.20:57738] mod_fcgid: stderr: PHP Warning: Use of undefined constant WPRSS_VERSION – assumed ‘WPRSS_VERSION’ (this will throw an Error in a future version of PHP) in /var/www/vhosts/workforce180.com/httpdocs/wp-content/plugins/wp-rss-feed-to-postXXX/wp-rss-feed-to-post.php on line 108, referer: https://workforce180.com/wp-admin/user-new.php

[Mon Dec 16 16:41:59.667726 2019] [fcgid:warn] [pid 29791:tid 139898124220160] [client 98.217.169.20:57738] mod_fcgid: stderr: PHP Warning: Use of undefined constant \xe2\x80\x98WPMS_ON\xe2\x80\x99 – assumed ‘\xe2\x80\x98WPMS_ON\xe2\x80\x99’ (this will throw an Error in a future version of PHP) in /var/www/vhosts/workforce180.com/httpdocs/wp-config.php on line 88, referer: https://workforce180.com/wp-admin/user-new.php

dwinden,

Worked as advertised, thanks so much.

Andrew

>>Go under the Advanced Tab and next to Include in Sitemap select Never Include
>>

Don’t see this in my version, using the free version. Is it not available in the free version ?

Thanks, I was hoping for an easier answer.

Viktor,

Are you using 3.6.6 for new installs or the Ithemes latest version.

Thanks for all your other helpful posts.

Andrew

WTF when are these guys going to get their act together.

Am I the only one upset that Ithemes has taken a great working plugin and broke it.

In addition they are hoping to SELL it !!!!

Gerroald

Let me make certain I fully understand your response. You guys take a functioning plugin. Then promise us numerous cool features and a PAID (!!!) version. Your next release breaks thousands of sites, after more than a dozen upgrades. Many continue to have problem. You refuse to acknowledge the problem or even attempt to explain.

Now people are asking for a “removal tool”. Think that sums up it.

And your response is we want YOU to take time from your busy day fixing our lousy plugin and submit a feature request.

You got some nerve.

>> <<

Hey 411plumb,

I’m sorry you’re having these issues. We’re working hard to get everything functioning properly for everyone. I think a removal tool is a great idea. If you’d like you can file a feature request here – iThemes Security Feature Request

Hey is is safe to go back in the water ? In other words are people able to safely upgrade to the newer version ?

I’m a bit confused this big (smart ??) company took over a great working program released 16 different upgrades. Created numerous problems in the process. Not only have they remained silent during the process they are hoping that we will pay money for a better version.

Hey wait now it all makes sense. Create a sh!!!ty product and then sell a better one.

Hmm, now we are up to version 4.0.16. This version is another failed attempt to fix the problems that surfaced in 4.0.7. People continue to have issues.

This means that the folks at iThemes have tried NINE TIMES to fix this problem and are still failing.

Have you ever know a competent software company to release NINE bugs fixes and each any everyone of them FAIL !!!

What’s worse is their silence.

Yikes I am still watching by the sidelines after issues with both 4.0.7 and 4.0.8. I am waiting for 5.0.

The more daring they may want to try using the Sandbox plugin to mitigate issues with crashing site.

My heart goes out to you guys, this really must be a tough issue to fix.

Best,

Andrew

>>
Still not working. I did a clean install of 4.0.7. When I activate I am kicked out of WordPress. When I try and access the dashboard I get “You do not have sufficient permissions to access this page.”. Thus I am forced to renamed “better-security” to access the dashboard.

Guess I gotta wait for 4.0.8
>>

Tried 4.0.8 exact same response.

Still not working. I did a clean install of 4.0.7. When I activate I am kicked out of WordPress. When I try and access the dashboard I get “You do not have sufficient permissions to access this page.”. Thus I am forced to renamed “better-security” to access the dashboard.

The guys at WordFence are probably laughing their assess off.

Guess I gotta wait for 4.0.8

Wow that was fast. Many thanks. Cool plugin