Every node has a "Submitted by USERNAME" line.

If a user changes his username, the following happens:

1. His username is not changed in the nodes. They still say "Submitted by OLDUSERNAME"

2. While 1 is true and the user is logged in he sees the new username in the nodes, but this is not true for any other users. When the user disconnects, he sees again his old username on the nodes.

3. The user gets blocked and cannot log in via any username. He needs to ask for a new password in order to log in again.

BTW the textboxes turn red in some ocassions and this has many problems, many people cannot see them and the Konqueror/KDE spellchecker doesn't work on red textboxes.

CommentFileSizeAuthor
#7 user_clear_cache_0.patch674 bytesprofix898
#5 user_clear_cache.patch639 bytesprofix898

Comments

TDobes’s picture

TDobes commented
Title: No username change in nodes after username change in database » Need to clear page cache after change in username

It sounds like problems #1 and #2 are caused by caching. It sounds like we need to call cache_clear_all() after a user changes his/her username. I'm changing the issue title appropriately.

Problem #3 is entirely different and belongs in a separate issue entirely. I should also note that I cannot duplicate this problem in 4.5.x or CVS HEAD.

The other problem you mention, seems to be a bug in Konqueror related to our red styling of the fields marked as errors. Please create a new bug report for this problem, listing the version of Konqueror you're using and a series of exact steps to replicate the problem.

TDobes’s picture

TDobes commented

Oops... looks like you already had a bug open for the error border problem in Konqueror. My mistake.

forngren’s picture

forngren commented
Version: 4.5.2 » x.y.z
magico’s picture

magico commented

This is a really old issue, forngren did you confirm this bug?

profix898’s picture

profix898 commented
Status: Active » Needs review
StatusFileSize
new user_clear_cache.patch639 bytes

I can confirm this bug. It only appears with page cache enabled (of course) and - as pages are not cached for logged-in users - only anonymous users dont see the username change. The patch simply calls cache_clear_all(), what (called without arguments) clears the page cache. It works nice, except when a minimum lifetime for cache objects is forced. In that case the page is updated after the selected lifetime is over.

As we flush the whole 'cache_page' table, it might have certain impact on sites with high anonymous user traffic. But a username change is a rare incident, I think.

Kjartan’s picture

Kjartan commented
Status: Needs review » Needs work

Wouldn't this patch clear all the cache on every user change and not just the name changes?

profix898’s picture

profix898 commented
Status: Needs work » Needs review
StatusFileSize
new user_clear_cache_0.patch674 bytes

Yes, you're absolutely right. Sorry :( This one is better - I hope!

AmrMostafa’s picture

AmrMostafa commented

Applied the patch, problem solved.

moshe weitzman’s picture

moshe weitzman commented
Version: x.y.z » 5.x-dev
Status: Needs review » Reviewed & tested by the community

works as designed.

dries’s picture

dries commented
Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD. Thanks.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)