Node: Has new content didn't update

I have this issue too. Hopefully someone can find a fix. I don't see anything. I ran update.php cleared my site cache.... 2.13 and 2.14 both have this issue so I have a big security hole since I rather my users be able to use my site without getting 1500 emails that nothing is updating for them.

Odd though... it only goes back to about 2 months ago. Stuff before that shows it was read and has no "new content" field showing.

There has to be an easy solution I'm missing.

Same behavior here.

If it's such an critical issue you should take at least 5mins to search. I can name you many issues in the issue queue which are the exact same issue, and yes the security fix causes this bug, i'm sorry for this.

http://drupal.org/node/1330716

Wow, did look for much longer than 5 minutes. Obviously you didn't. The patch you are talking about didn't work, so no, not the same issue. Thanks for being so completely negative and combative.

Did you really tried out the patch in http://drupal.org/node/1330716#comment-5200418 ?
Multiple users said that this patch worked. If this patch didn't worked for you, you should provide more information.

Actually i think having a real security hole on your site is much more worse, then showing some wrong nodes in a listing.

I'm glad your an expert in human psychology. Considering I have yet to see what this supposed 11 month old security hole is, I think I rather keep members on my site for a couple days and not roaming elsewhere.

Yes I really tried the patch. I still had posts showing the tag for a new comment even after the node has been viewed. It affected all nodes or comments that were less than 3 months old. I had to reinstall the module again, clear all caches again, update the database again and apply the patch, then clear and update again to get it to work finally. Yes, my next step was a human sacrifice, possibly getting dogs and cats to live together, whatever it took at that point.

No where in my issue or the OP's issue did we say we were looking for "Views substitutions broken after db_safe() update" we just knew the new comment tag was not going away. So your initial sarcasm only added to my frustration with this.

Instead of patchworking my modules, which doesn't sound so safe anyway, it shouldn't be much to hope for a release that includes the proper code. Thanks!

Latest version fixed this as well

more description