Zade

@omarfpg As stated above, could you (and your entire team) please refrain from marking this ticket “Resolved” until you have added a single space to that CSS file? This is not resolved, so marking it as such is dishonest, and it makes your customers think you are no longer concerned about this. If you think about it, it would be faster to type one space in one file than to type yet another response in this thread, notifying everybody that is following and wasting even more time. So do the right thing for all of us, including you. Otherwise I guess we can all look for a more supported payment gateway. Thanks ??

@eddivalen I still don’t understand why there’s any talk of “generating the source map”. The fix is to edit a CSS file that improperly comments out a reference to another file (a .map file), because while:

/* #this */

is a comment that’s ignored,

/*#this */

isn’t because there is no space between “/*” and “#”. But edits to plugin files are overwritten when the plugin is updated. So the plugin authors need to make this change to the CSS file so the fixed file gets published to the WordPress repository.

@eddivalen Not sure what you’re talking about. Did somebody say that the authors won’t be simply adding a space to that CSS file and I have to generate a source map file instead?

@gabrielfuentes Could you please refrain from marking this ticket “Resolved” until you have added a single space to that CSS file?

Hi @shameemreza,

Posting here so others with the same question see this. I think I understand what’s going on. The “problem” we are all reporting is less of a problem and more of a confusing interface. After switching to HPOS, the following message now only applies to compatibility mode, but its wording suggests that it is still preventing HPOS from being fully active:

There are 3 orders pending sync. You can switch order data storage only when the posts and orders tables are in sync.
Sync 3 pending orders

If you don’t enable compatibility mode, this message will (eventually) appear regardless, but after switching to HPOS this message should only appear when the “Enable compatibility mode” checkbox is checked. That’s because it’s irrelevant whether your posts and orders tables are in sync if you’ve already synched and activated HPOS. No orders should end up in the posts table after enabling HPOS without compatibility mode, right? So don’t present a scary bold message to users who don’t need to see it. And don’t tell us something is “pending” when in reality it does not require our attention. In addition to conditionally hiding this message, the second sentence should be removed altogether once a user has switched to HPOS:

You can switch order data storage only when the posts and orders tables are in sync.

That sentence is technically incorrect when HPOS is active because it speaks of a future event (switching order data storage) that has already transpired. At this point it technically should say:

If you ever switch back to legacy storage and then decide to enable HPOS again, you will need to resync the posts and orders tables.

But it’d be less confusing to just hide that sentence after HPOS is successfully enabled, then show it again only in the rare event that a user switches from HPOS back to legacy storage. From a programming standpoint, the logic is simple:

1. If orders pending sync > 0:
   • If Order Data Storage legacy radio button = selected:
     • Show link to sync orders and message “You can switch order data storage only when the posts and orders tables are in sync.”
   • Else if Compatibility Mode checkbox = checked:
     • Show link to sync orders and message “Compatibility mode will be fully enabled when the posts and orders tables are in sync.”
   • Else: Hide message and link to sync orders
2. Else: Hide message and link to sync orders

Hi @shameemreza,

Is the wc_run_batch_process task responsible for manual syncing (when clicking “Sync X pending orders”) or for preventing the “Sync X pending orders” message from appearing in the first place?

The issue we’re having is not the former (getting the message to disappear when manually clicked) but rather the latter (preventing the message from reappearing after being in sync). On the now 3 sites where I’ve enabled HPOS, all wc_run_batch_process tasks show a Status of “Complete” and the button to “Delete the custom orders tables” is greyed out. Also I have not enabled compatibility mode.

I manage dozens of sites and don’t want to install yet another plugin like WP Crontrol to avoid this recurring message.

Thanks.

I have the exact same issue on both of the sites where I’ve enabled HPOS. I sync, the sync message disappears, the HPOS radio button is active again (and selected), then when a new order comes in, the sync message appears again.

@harleec did you get this resolved?

Hi @vmarko and thanks for working on this.

Yes, the warnings are identical, with W3TC version 2.7.2 and the latest version of WordPress and all themes/plugins updated. I did some further testing, and the first batch of warnings only appears when viewing the Performance Dashboard (/wp-admin/admin.php?page=w3tc_dashboard):

PHP Warning: Undefined array key "interval" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 15
PHP Warning: Undefined array key "since" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 18
PHP Warning: Undefined array key "interval" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 23
PHP Warning: Undefined array key "until" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 26
PHP Warning: Undefined array key "bandwidth_all" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 38
PHP Warning: Undefined array key "bandwidth_cached" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 39
PHP Warning: Undefined array key "requests_all" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 43
PHP Warning: Undefined array key "requests_cached" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 44
PHP Warning: Undefined array key "pageviews_all" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 48
PHP Warning: Undefined array key "uniques_all" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 52
PHP Warning: Undefined array key "threats_all" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 56
PHP Warning: Undefined array key "cached_tf" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 59
PHP Warning: Undefined array key "cached_ts" in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Widget_View.php on line 59

If I go into Extensions > Cloudflare > Settings and Reauthorize, this batch of warnings ceases.

On some of my 80 sites, like my test site (wordpress.pillerdesigns.com), the other warning appears to have resolved itself (without having to Reauthorize):

PHP Warning: Undefined array key 1 in /wp-content/plugins/w3-total-cache/Extension_CloudFlare_Plugin.php on line 390

Maybe it helps that this testing site hasn’t had W3TC continuously active for the past year. However, on many of my sites, like onadrapery.com and bobwells.org, this warning continues to appear once on every front-end page load and 1-4 times or more on every back-end page load or request. I have tried reauthorizing after deactivating/reactivating the Cloudflare extension and then purging all caches, but the warning persists. I also tried deactivating/reactivating W3TC. Interestingly, sometimes clicking Deactivate under Cloudflare on the Extensions page just reloads the page, and it takes a few tries to actually deactivate this extension. Also the warning appears with every front-end page load when logged in but only sometimes when refreshing the homepage without being logged in.

I can give you access to my testing site, if you’d like, where I haven’t yet done the reauthorization to clear the first batch of errors. My hope is that both sets of warnings can be resolved without having to reauthorize 80 sites. The reauthorization is especially annoying because the Cloudflare domains are split into 5 pages, so I can’t simply scroll to click the associated domain’s radio button. On sites that still show the second warning, this warning also appears when clicking to a new page of results in your Cloudflare authorization popup.

Finally, this is probably a separate issue, but in case it helps, on a couple of my sites, like flowscreens.com, I have never been able to get rid of the “One or more plugins have been activated or deactivated, please [empty the page cache] [hide this message].” notification, no matter how many times I click [empty the page cache] or [hide this message]. This has been the case for years, even after deleting the plugin and reinstalling without importing a backup of my settings. I believe I reported this is another ticket a long time ago.

• This reply was modified 6 months, 1 week ago by Zade. Reason: added more information

Thanks for the quick reply. I just confirmed this issue with the default Woo theme (Storefront) and latest WP theme (Twenty Twenty-Four). No plugins active except yours and WooCommerce. May I ask which exact version of PHP you are running? This site uses PHP 8.2.16.

I tried both of the Save buttons at /wp-admin/admin.php?page=cix-gallery-settings, as well as clearing all caches before/after clicking, and I still see two of the same warning with every product page load.

Pretty hilarious that the developers can’t simply add a single space to a single file in six months. I’m guessing they haven’t even been notified.

In case this helps, cPanel’s WP Toolkit reports the issue as follows:

WordPress Popup Anything plugin <= 2.7.0 – Broken Access Control vulnerability

Sure, here’s the exact output on two sites I tried:

CREATE TABLE wp_itsec_geolocation_cache (
location_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
location_host varchar(40) NOT NULL,
location_lat decimal(10,8) NOT NULL,
location_long decimal(11,8) NOT NULL,
location_label varchar(255) NOT NULL,
location_credit varchar(255) NOT NULL,
location_time datetime NOT NULL,
location_meta text NOT NULL,
PRIMARY KEY (location_id),
UNIQUE KEY location_host (location_host),
KEY location_time (location_time)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci

The error doesn’t repeat for the same site, but it did happen for all 100+ sites a single time, right when I updated. The chance of some database fluke happening that many times is infinitesimally small. Anyway, my sites appear to be loading fine, just wanted to let you know.

Hi @nlpro,

Thanks for your response. Not sure if your “Updated wrong topic” comment refers to the one you changed to that or both comments, but a random database issue seems unlikely since it’s happening on all of my sites, not just one. Anyone, I checked one, my build is 4128, and I have all 14 tables:

wp_itsec_bans
wp_itsec_dashboard_events
wp_itsec_dashboard_lockouts
wp_itsec_distributed_storage
wp_itsec_fingerprints
wp_itsec_firewall_rules
wp_itsec_geolocation_cache
wp_itsec_lockouts
wp_itsec_logs
wp_itsec_mutexes
wp_itsec_opaque_tokens
wp_itsec_temp
wp_itsec_user_groups
wp_itsec_vulnerabilities

I have, and I’m in the same boat as David.