Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
David N. Posted August 15 Posted August 15 (edited) This is weird? EDIT: emptying the cache in my browser cleared the red alert and #1 indicating that there was a topic to approve. But that's the first time I see this behavior, the alert normally clears automatically when I approve the topic. LogicPro11-c08.mp4 Edited August 15 by David N.
Management Matt Posted August 15 Management Posted August 15 Next time you see an errant approval flag, leave it and see if it clears itself. We made a lot of changes to how counts and node last info is built to reduce MySQL load. To safeguard against any random issues, there is a task that runs every 5 minutes or so to tidy up any potential issues. We'll look into the core issue of course, but you may find it fixes itself in a few minutes. David N. and Marc 2
David N. Posted August 15 Author Posted August 15 Ok @Matt I'll try that. I guess I'm used to this workflow: I see a number of unapproved topics and/or posts, I approve one or two, I go back to the home page and if I still see some, I click them to approve them. ... and I know I'm done once I no longer see any approval flags on my home page. But yes if this reoccurs I'll try to just wait 5mn.
Management Matt Posted August 15 Management Posted August 15 Just now, David N. said: Ok @Matt I'll try that. I guess I'm used to this workflow: I see a number of unapproved topics and/or posts, I approve one or two, I go back to the home page and if I still see some, I click them to approve them. ... and I know I'm done once I no longer see any approval flags on my home page. But yes if this reoccurs I'll try to just wait 5mn. That's how it should continue to function, so we can look at that. But it should fix itself in a few minutes until we get a fix out. David N. 1
David N. Posted August 24 Author Posted August 24 (edited) I'm having this issue again right now. LogicPro11.mp4 Edited August 24 by David N.
David N. Posted August 25 Author Posted August 25 23 minutes ago, Jim M said: This has fixed itself as Matt mentioned above 😉 Indeed it has. So there's no need for me to continue reporting those I suppose?
Jim M Posted August 25 Posted August 25 2 minutes ago, David N. said: Indeed it has. So there's no need for me to continue reporting those I suppose? Correct. Until we release a fix for the issue overall that you're experiencing. David N. and SeNioR- 2
David N. Posted August 25 Author Posted August 25 10 minutes ago, Jim M said: Correct. Until we release a fix for the issue overall that you're experiencing. Great, that makes sense. Thank you!
Solution David N. Posted 23 hours ago Author Solution Posted 23 hours ago This appears to be fixed in v4.7.19. Yoohoo! 🙂 Jim M 1
Recommended Posts