A while back when I updated Toolset, the WordPress notification for a plugin update didn't go away. I see in future udpates that one of the changelog items says something about fixing that - but it has never been fixed for me. My WordPress notification item ALWAYS shows that one plugin needs updating, even though all of my plugins are up to date.
Could you please share access details so I can check further.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I would additionally need your permission to de- and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important. If you agree to this, please use the form fields I have enabled below to provide temporary access details (wp-admin and FTP).
I have set the next reply to private which means only you and I have access to it.
I know that there is no plugin that says it needs to be updated - but WordPress has a notification of "1" at the top (see screenshot).
This started several months ago when I performed a Toolset update and got an error that it had "failed". I did the update over again, and have never gotten the "failed" error message again, but my WordPress notifications continue to have that "1" even though there is nothing to be updated.
I believe that it is coming from Toolset because it started several months ago when I did a Toolset update and got a message that the update had failed. I tried again and did not get the error, but the notification remained and has never gone away since.
Well - the thing is that I am not able to see this issue on my test site and furthermore even I do not see this is caused by Toolset. I need evidence that will help me to present in front of our Devs and I checked but I do not see anything related to Toolset as far as I can see.
If you find something to share that it's really caused by Toolset we are happy to investigate further otherwise feel free to close the ticket.