I have the same issue. It is extremely annoying especially when it cannot be dismissed and it throws you back to the home page. It would be nice if this could be fixed.
Hi there @galbaras and @joseph603i
Could you try downgrading to version 3.5.1 of the plugin (directly linked here) and see if the issue persists, please?
An alternative way, would be to utilize the WP Rollback plugin for doing so.
Looking forward to your responses, thank you.
I’d rather wait for the next release. It’s not a big enough problem to roll back actual fixes.
OK! Just to note, you might want to enable auto-updates for the plugin (related documentation on how to do so, linked here), unless they are already enabled. This way, the update will be applied directly when available and a notification message about that will arrive in your email inbox.
Have a wonderful day! 🙂</img>
All too often, I see releases that need fixing within a day, or even a few hours, sometimes after crippling some sites. There’s simply no way for plugin authors, however well-meaning, to test every possible scenario.
So I’m going to wait and apply the next release manually, after vetting it.
As a provider of professional WordPress administration services, I never update anything less than 2 days from its release, and I urge you not to suggest automatic updates to anyone.
This is all fine if there is an update coming soon, but if it is going to take months or even weeks, removing a display message from the code should not be that hard. I don’t want to rollback to an older version just because an display message won’t go away.
Roxy
(@roxannestoltz)
Hi @galbaras ,
If you prefer not to rollback to a previous version, and the notice is something you would like to remove from being displayed, you can do so by using the following SQL query in your phpmyadmin to delete the notice from the wp_wc_admin_notes table:
DELETE FROM wp_wc_admin_notes
WHERE name = 'needs-update-eway-payment-gateway-rin-2022-12-20';
Please let us know if that helps!
Turns out there’s a updated-eway-payment-gateway-rin-2022-12-20 admin note, but it’s later than the other one, and set to pending, whereas the undismissable one is set to unactioned.
Also, for consistency, the related records in wp_wc_admin_note_actions should also be deleted. Otherwise, they will be orphaned.
Not everyone is comfortable running SQL queries. A better option is to release a version of the plugin that works correctly. Shouldn’t take too long, given that the plugin itself won’t change.
We’ve been at it for over a week. It’s time to fix the issue.
Hi,
I can understand your point.
To help you investigate more about this issue, can you please share a copy of your site’s System Status Report? It is under WooCommerce > Status. Select “Get system report” and then “Copy for support”.
Thank you.
Sorry, I’m not spending any more time on this. It’s very minor and I’ve applied the workaround to it.
But there’s nothing special about my site, and my other sites don’t even display those messages (I use a plugin that disables the new WC admin interface).
I agree this is waste of time. We should not have apply workarounds or anything else. Just simply remove this meaningless message from the code.
The easiest solution is to switch to another plugin.
@joseph603i Please stick to the forum code of conduct and be respectful, even when you are frustrated.
The main feature of this plugin is accepting payments via eWay, and that is working well, even there are some minor issue, especially when the plugin team is trying to fix things.
I have a different message that I also can’t dismiss:
WooCommerce Eway Gateway has been automatically updated
Your store is now running the latest secure version of WooCommerce Eway Gateway. We worked with the WordPress Plugins team to deploy a software update to stores running WooCommerce Eway Gateway (versions 3.1.0 to 3.5.0) in response to a security vulnerability that was discovered.
Every time I click Dismiss and reload the page, the message comes back.
Version 3.5.2.
I am having the same issue.. click dismiss.. and it comes back. I tried deactivating and reactivating.. issue still exists..
Roxy
(@roxannestoltz)
Hi @globalmatt and @lukestorm ,
I understand that you are experiencing the same issue.
If the suggested workarounds shared in this thread are not working for you, and you would like further help, would you please start your own topic.
Since you’re not the person who originally started this topic, per the forum guidelines, you would need to create your own topic.
We’ll be more than happy to help there.
