mfarmerhi

Oooohhh… that was your workaround? You’re using the BBPress archive to display on twenty twentytwo theme?

Is there no full uninstall for bbp style pack? Even after deleting the plugin, all data remains in the database.

Thank you, I have run the set-up wizard again. Developers may reconsider the wording or an alternative notice if others find confusion in being requested to set up an already set up LearnPress installation. Thanks for your help.

Why in the world would I run the setup wizard when the plug-in is already set up?

I’ve never had to run the wizard a second time simply because the plug-in was updated.

Again, the plugin has already been configured. This was only an update. Running the wizard again would overwrite the currently configured settings, no?

“Deactivating and deleting the plugin also works.”

+1

Unfortunately that was my decision too. When other news sources announce such vulnerabilities and the plugin author hasn’t yet addressed it… the cat’s out of the bag. No excuse in my opinion.

+1
Resolved w/fix given by katereji (@katereji)
Hoping stable 5.161.3 / official release will include
thanks

Awesome, thanks for the quick reply and the plugin!

Awesome plugin, just installed and one related question to your answer on this thread:

Am I understanding correctly that, if global redirect is not set AND product redirects are not set, customer will be redirected to default Woocommerce order details page? Is that correct?

Thank you for helping me to understand.

Resynched with cloud; appears resolved; ticket closed

JQuery errors still reporting in woo-cart-abandonment-recovery/admin/assets/js/admin-email-templates.js line #452: \’hover\’ pseudo-event is deprecated, use \’mouseenter mouseleave\’

??

The program would simply need to skip the portion interacting with Paypal. Certainly editing the PHP would accomplish this.

Regarding (copied verbatim):

Header always set Strict-Transport-Security: "max-age=31536000" env=HTTPS
Header always set X-XSS-Protection "1; mode=block"'
Header always set X-Content-Type-Options "nosniff"
Header always set Referrer-Policy: "no-referrer-when-downgrade"
Header always set Expect-CT "max-age=7776000, enforce"
Header always set X-Frame-Options "sameorigin"
Header always set Content-Security-Policy "upgrade-insecure-requests"

Wild goose chase: the apostrophe [‘] renders your suggested changes unusable.

Add those in *WHERE* in .htaccess!?

Because adding them in anywhere – from the beginning to inside your RS SSL coding to tacking on the end – resulted in a 500 error.

Honestly, rather than upgrading to pro… I think it’d be easier to just delete the plugin and move on to something that’s not hell bent on trying to separate me from my $$$

Yes, preserving option data upon switching would save a TON of time for users. Thanks for considering it.