Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When handling the comment flags, I noticed the following two comments being flagged.
Since the flagger was not the user who posted the comment, and I was not understanding why the comment would be flagged as spam, I clicked on View, and noticed that the user who posted the comment is davps.
The user changed username, but the view still used the old username to show the author. I take this is a caching issue.
I set the priority to Minor, but it's really important for the users who handle flags to understand if the flag on a comment was raised from the user who posted the comment, as those flags are immediately discarded because the user probably mis-clicked on report as spam. (I doubt users would mark their own comments as spam.)
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot.191012.1205.png | 32.94 KB | apaderno | |
| Screenshot.191011.1541.png | 28.28 KB | apaderno |
Comments
Comment #2
drummComment #5
drummThis is now fixed. It wasn’t caching specifically, Drupal comments have a name column in the comment table, which is not updated with user updates, and that was being displayed.
Comment #6
apadernoI forgot I reported the same problem for a view showing a list of comments used on api.d.o, for which the cause was the view taking the username from the comment database table, like in this case. (Yes, assuming the cause was caching was totally wrong from my side.)