ftjs2025
Forum Replies Created
-
Would be best if they had better naming, but I wrote a small snippet to remove the messages with css:
add_action( 'admin_head', function() {
echo '<style>
#message.updated.woocommerce-message {
display: none !important;
}
</style>';
});For every one else who wants these messages gone, you can use that to surpress these notices.
Thanks for the message. So, 2 things. 1st: it says: Facebook for WooCommerce – 3.4.7 is untested with WordPress 6.8.1. Which version of WordPress shall we use then?
2nd: Class nominator attributes called “updated woocommerce-message” was indeed part of woocommerce specs. Yet, it’s not even factual, because the message doesn’t come from woocommerce. I’d argue that this is neither functional nor best UX.I’m really sorry to write you here complaining, but these pretentious unmutable messages, it really bothers us.
I found a solution that worked, and it was buried deep in the code, quite a feat to isolate.
In \facebook-for-woocommerce\vendor\woocommerce\grow\src\Checks\WCCompatibility.php
just completely replaced the get_latest_wc_versions function like this:private function get_latest_wc_versions() {
// Return an empty array instead of trying to fetch and set the transient
return [];
}
Finally, no more annoying messages. Took a couple of tries until I found the actual source of the message. As it the message didn’t even have a custom css class that could be filtered for.
You know, you told me the same some months ago. The message was briefly gone, but came back the release after that. Just remove it for good. Really no need to have such resilient admin messages for such a low-priority issue like version not tested.- This reply was modified 1 year, 1 month ago by ftjs2025.
It’s really annoying. Worse than that, this message is set by url-flag. On dismissal, it sets a flag in the url, and as soon as you change to a different page, message is there again.
The issue is in the bug tracker now: https://github.com/facebook/facebook-for-woocommerce/issues/3020
I want to add that I noticed why the message is coming back. They just add an url flag, to hide the notice. This is quite an unprofessional way to work with wordpress notifications, and seems like it was conceived by copilot or something like that. I wish you had a little more quality control and would fix this once and for all.@iodic @marijastuntcoders @vinkmeta Hello there,
So the message is back:
“Facebook for WooCommerce – version 3.4.4 is untested with WooCommerce 9.7.1.”
and still can’t be dismissed. I comes right back, and I can’t understand how you don’t properly design an admin message. It would be all fine if we could just hit “dismiss” and the message would be gone. But hitting “dismiss” to only see it come back next time I reload the page, is not only annoying, but makes us question what’s going on with your development. Just make the message dismissable, or is that too much to ask? My boss is hounding me each time this pops up, and frankly I’ve got better things to do than to complain to you here. Please fix it, you could put a unit test there to see if dismissal really worked, and just keep it working going forward.
Hello there @marijastuntcoders, @iodic
So, this message is back, for current version number, and keeps coming back even if dismissed.
>Facebook for WooCommerce – version 3.4.3 is untested with WooCommerce 9.7.1.
It’s really really really annoying. Please, if you could offer a fix going forward, that would be highly appreciated! All we want is being able to dismiss messages like that for good. Thank you!