Title: Paul's Replies | WordPress.org --- # Paul [ ](https://wordpress.org/support/users/kloudstack/) * [Profile](https://wordpress.org/support/users/kloudstack/) * [Topics Started](https://wordpress.org/support/users/kloudstack/topics/) * [Replies Created](https://wordpress.org/support/users/kloudstack/replies/) * [Reviews Written](https://wordpress.org/support/users/kloudstack/reviews/) * [Topics Replied To](https://wordpress.org/support/users/kloudstack/replied-to/) * [Engagements](https://wordpress.org/support/users/kloudstack/engagements/) * [Favorites](https://wordpress.org/support/users/kloudstack/favorites/) Search replies: ## Forum Replies Created Viewing 8 replies - 1 through 8 (of 8 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Feeds for YouTube (YouTube video, channel, and gallery plugin)] Generating malformed CSS URLs](https://wordpress.org/support/topic/generating-malformed-css-urls/) * Thread Starter [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [1 month, 3 weeks ago](https://wordpress.org/support/topic/generating-malformed-css-urls/#post-18879047) * Hi [@smashballoonlouis](https://wordpress.org/support/users/smashballoonlouis/) Just to confirm, based on the fix for version 2.6.2, does this also apply to version 2.6.3? If a customer is already on 2.6.3, should they use this fix file as well? * Also, will the custom 2.6.3 fix resolve the Elementor issue? * When testing this on our custom staging environment, the YouTube Feed Elementor widget did not update correctly. The content tab would not display, and the feed settings dropdown was missing. As a result, the user would need to use the shortcode instead. * ![](https://wordpress.org/5339356a-54e0-4e52-936c-7e1a1c1e1bd2) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Feeds for YouTube (YouTube video, channel, and gallery plugin)] Generating malformed CSS URLs](https://wordpress.org/support/topic/generating-malformed-css-urls/) * Thread Starter [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [1 month, 4 weeks ago](https://wordpress.org/support/topic/generating-malformed-css-urls/#post-18877723) * Hi [@smashballoonlouis](https://wordpress.org/support/users/smashballoonlouis/) Thanks for the feedback, question is the link is it just a rollback to 2.6.2 from 2.6.2ThanksPaul * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Feeds for YouTube (YouTube video, channel, and gallery plugin)] Malformed CSS URLs](https://wordpress.org/support/topic/malformed-css-urls/) * [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [2 months, 1 week ago](https://wordpress.org/support/topic/malformed-css-urls/#post-18864785) * Hi [@smashballoonlouis](https://wordpress.org/support/users/smashballoonlouis/) Was the fix made for the malformed CSS URLs in the last version update?ThanksPaul * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence MFA Fails on Multi-Instance Setup (Azure App Services + AFD)](https://wordpress.org/support/topic/wordfence-mfa-fails-on-multi-instance-setup-azure-app-services-afd/) * Thread Starter [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [5 months, 3 weeks ago](https://wordpress.org/support/topic/wordfence-mfa-fails-on-multi-instance-setup-azure-app-services-afd/#post-18756230) * Hi [@wfpeter](https://wordpress.org/support/users/wfpeter/) Thanks for your reply. Here is a clearer summary of the issue on our **multi-instance WordPress setup (Azure App Service, 2+ backend instances)**.**Issue Description** * After entering a valid 2FA code, the login page reloads and eventually displays: * > **“CODE INVALID: The 2FA code provided is either expired or invalid. Please > try again.”** * This only occurs when the 2FA validation request is handled by a **different instance** than the one that generated the MFA challenge. With **1 instance**, Wordfence MFA works perfectly. * **Note:** The user _can_ eventually log in, but only when the request happens to land back on the same instance where the MFA challenge was originally created.** Cause Identified** * The issue occurs when the following W3 Total Cache setting is enabled: ❌ **Enable caching for wp-admin requests** * When enabled, wp-admin and MFA-related pages are cached, causing: - MFA token generated on Instance A - Validation request processed on Instance B - Instance B lacks the required MFA transient/nonce - Wordfence returns the “invalid code” error - Login loops * Disabling wp-admin caching resolves the issue immediately. ✔️ The following setting is safe to keep enabled: * **Store transients in database** This ensures MFA-related transient data is shared across all instances.**Request for Guidance** * Could you please confirm Wordfence’s recommended configuration for: - Multi-instance / load-balanced WordPress environments - Using Wordfence MFA with caching plugins - Any wp-admin caching settings that should remain disabled for compatibility * Thanks again * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[W3 Total Cache] Setting: Prevent caching of objects after settings change](https://wordpress.org/support/topic/setting-prevent-caching-of-objects-after-settings-change/) * Thread Starter [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [1 year, 4 months ago](https://wordpress.org/support/topic/setting-prevent-caching-of-objects-after-settings-change/#post-18291341) * Hi [@vmarko](https://wordpress.org/support/users/vmarko/) In most cases, it’s applied to all media types. * .docx?x37618&x37618″ .pdf?x37618&x37618″See below how it applies only to the first src= .jpg?x37618&x37618″
””
* Thanks * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[W3 Total Cache] Setting: Prevent caching of objects after settings change](https://wordpress.org/support/topic/setting-prevent-caching-of-objects-after-settings-change/) * Thread Starter [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [1 year, 4 months ago](https://wordpress.org/support/topic/setting-prevent-caching-of-objects-after-settings-change/#post-18278782) * Hi Marko, * Yes, I did also send a support email… So based on my testing the key finding was that W3 Total cache applies different configurations for Apex/Root domain vs. Subdomains. * Since the duplicate query string issue (?x71967&x71967) appears in the HTML source code, this confirms that W3 Total Cache (W3T) is generating the duplicate versioning before the request even reaches Azure Front Door. * Additionally, the fact that subdomains (cdn.saaslabs.com.au) do not have the issue, while root domains _[ redundant links deleted ]_ do, means W3T is applying different caching logic depending on the domain type. Is there any thing that I can review further on my end? Or a workaround? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Issue Updating to Version 24.3](https://wordpress.org/support/topic/issue-updating-to-version-24-3/) * [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [1 year, 4 months ago](https://wordpress.org/support/topic/issue-updating-to-version-24-3/#post-18274576) * Sorry, all has been resolved it was the WAF 😊 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Issue Updating to Version 24.3](https://wordpress.org/support/topic/issue-updating-to-version-24-3/) * [Paul](https://wordpress.org/support/users/kloudstack/) * (@kloudstack) * [1 year, 4 months ago](https://wordpress.org/support/topic/issue-updating-to-version-24-3/#post-18274446) * On the WordPress Dashboard, there is the following * Install latest Yoast SEO Yoast SEO 24.3 must be installed and activated to use Yoast SEO Premium.——————————- * Installing Plugin: Yoast SEO 24.3 * Downloading installation package from [https://downloads.wordpress.org/plugin/wordpress-seo.24.3.zip…](https://downloads.wordpress.org/plugin/wordpress-seo.24.3.zip…) * Unpacking the package… * Installing the plugin… * Destination folder already exists. /home/site/wwwroot/wp-content/plugins/wordpress- seo/ * Plugin installation failed. * [Go to Plugin Installer](https://motorsport.org.au/wp-admin/plugin-install.php) ——————————— Note that I have already rename the folder Viewing 8 replies - 1 through 8 (of 8 total)