webbirddigital
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] [BUG] Dark mode css loading on website frontendI’ve created a pull-request with a fix, here: https://github.com/litespeedtech/lscache_wp/pull/923
Forum: Plugins
In reply to: [LiteSpeed Cache] [BUG] Dark mode css loading on website frontendAdditionally, the reason that your CSS rules are applying is that the
body[class*="litespeed"]:not(.litespeed-lightmode)is matching the frontend class.litespeed_lazyloadedwhich is applied to the <body> element when lazyloaded images are enabled.Forum: Plugins
In reply to: [LiteSpeed Cache] [BUG] Dark mode css loading on website frontendUpon further investigation, the bug here is a logical one. The
litespeed-dark-mode.cssfile is being loaded bylitespeed.cssusing@import url('litespeed-dark-mode.css?v=37');however thislitespeed.cssfile is loaded on the website frontend insrc/gui.cls.phpTo correct this, I suggest that
litespeed-dark-mode.cssinstead be loaded alongsidelitespeed.cssinadmin-display.cls.php, in the enqueue_style() function (and the @import rule removed from litespeed.css).eg.
public function enqueue_style() {
wp_enqueue_style( Core::PLUGIN_NAME, LSWCP_PLUGIN_URL . 'assets/css/litespeed.css', array(), Core::VER, 'all' );wp_enqueue_style( Core::PLUGIN_NAME . '-darkmode', LSWCP_PLUGIN_URL . 'assets/css/litespeed-dark-mode.css', array(), Core::VER, 'all' );
}Forum: Plugins
In reply to: [LiteSpeed Cache] [BUG] Dark mode css loading on website frontendI can’t seem to send a report. Getting error “Cloud Error: Please try after 4m 27s for service wp/report.”. Last report number shows: –
Note that we have observed this dark-mode bug on about 20 different websites after updating to 7.6 (version 7.5 is unaffected). This bug is not likely a plugin or theme conflict.
Same issue here when creating Repeating Events on version 7.2.1
Your event details are incorrect and recurrences cannot be created, please correct these errors first:
Main recurrence set times are required.Perfect! Confirmed fixed from our end.
Does this affect only back-end users or also front-end users?
This is affecting front-end users.
Note that we are using the standard modsecurity ruleset which comes preinstalled on WMH/cPanel servers. By default rules are set to alert only, but it is recommended that they are enabled on production servers.
Not really the way how you motivate any developer to do something for you.
There is a reason for this traversal and has to do with the local testing setup.It would motivate me 😉 Sorry if this came across offensively, that wasn’t my intention (it just was meant as a bit of a jab).
- This reply was modified 4 years, 11 months ago by webbirddigital.
Same issue here. Disabling the “User requested a password reset” event bypasses the issue as a temporary workaround.