rcain

Hi Paul,

Oh my goodness! You are absolutely correct. I’ve now found it. Thank you so much.

Got to admit though, pretty confusing interface design here – two entirely different config screens for essentially the exact same feature. I wonder if this might be improved in some future release?

PS: I’ve now also just discovered that 2FA is DISABLED IFF the IP address is whitelisted in Shield. Since this is my development machine I had whitelisted my IP address – hence 2FA emails were not being triggered for any of my tests. I deleted the whitelist entry and presto! 2FA email challenge now working as expected. Hoorah! (PPS: though thinking about it, whitelisted IP is but an additional authentication factor and arguably shouldn’t disable other existing authentication factors by default – selectivity perhaps another design suggestion for future/pro version?)

Thank you both – Paul & Jelena.

Have a great day 🙂

• This reply was modified 8 months, 3 weeks ago by rcain.
• This reply was modified 8 months, 3 weeks ago by rcain.

Sounds great. Very helpful. Thanks Lisa.

Best regards

Rob

Hi there,

Thanks for that. All good. I’ve discovered the culprit:

A small custom plugin I’d hastily written to add a ‘clear current page cache’ button to admin bar for selected user roles other than Admin (eg: shop-admin): I’d (very shoddily) protected the plugin from activating without lscache being active with a:

defined('WPINC') && defined('LSCWP_V') || exit;  

Which protects against activation BUT of course exits the whole thread if lscache is deactivated whilst this plugin still active. Hence the WSOD.

removed above, & instead used:

Requires Plugins: litespeed-cache

in the plugin header section – and all is good.

I hang my head in shame! 🙁

Thanks very much for your help qtwrk. Much appreciated.

Problem resolved.

• This reply was modified 1 year, 1 month ago by rcain.

Hi again,

Apart from your first line (!), all moderately sensible suggestions, thanks.

1. can run a flat html file from root – ok
2. can run phpinfo from file – all ok
3. lscache directory all empty at present (just skeleton dir structure) – since i flushed all LS cache from back CP end, that is expected.
4. wp-config.php – traced – all loading fine right up to last line (require wp-settings.php) so fine there so far as it goes
5. will continue diagnostic/tracing

But note well, this happened immediately upon deactivating lscache plugin. (FYI plugins most certainly can & do sometimes cause issues like this, most especially caching & redirection plugins).

I have to say, I’m becoming seriously concerned by the quality of lscache plugin of late – by my count no less than 3 critical security issues in the past year (baby stuff too!), just now the RUDE QUIC splash obscuring dashboard (see other thread), and now WSOD upon simple plugin deactivation.

Hi qtwrk,

Thanks for your reply. Indeed I found your ‘addon’ plugin on git hub & have forked & bastardized to my current requirements (just about). But really good to know we are both thinking along similar lines. Lets keep in touch.

All very best

Rob

Hi Hendra,

Thanks for your reply. I quite understand the problem.

Just to reiterate – the wpra/twig/use_translations filter solution doesn’t seem to work (though I haven’t determined why). The longer code mod solution does work however – which we can live with for the time being 🙂 .

Look forward to the new version later this summer. Great plugin. 🙂

Best regards.