Yes, the add-index CLI command has to be run on each site in a multisite. You can script it to run in a for loop and iterate over each site, but we’ll be pushing that in 1.4.2. In the meantime, the notices are dismissible and stay dismissed (but if you’re seeing it on sub-sites, you’ll probably see it on all sub-sites that haven’t gotten the update). I’m looking at the check I added to hide the notice on multisite and realize that I think the logic is flipped because it’s checking if the notice is dismissed or we’re on multisite, so one of those will evaluate to true on multisite.
At any rate, to answer your question, if you are no longer getting the notice on 1.4.0 and you just want the notice to go away, there’s no reason you couldn’t roll back to 1.4.0. The only danger there is the command can’t actually be run at all on sub-sites in 1.4.0, but if you’re not going to worry about that for the time being, it would be file to roll back.
Thanks, @jazzs3quence! I may have been a bit confused. I thought 1.4.1 would automatically hide the notice all throughout the multisite.
I did find that the message kept coming back after being dismissed on our test environment.
I’ve gone back to 1.3.6 for now.
I thought 1.4.1 would automatically hide the notice all throughout the multisite.
Not confused, that was the intention (at least as a temporary measure), just not executed correctly. But I’ll have to doublecheck the package based on your feedback because it seems like it was behaving like 1.4.0. 🤔
At any rate, you should be good for now.