Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I logged in https://localize-7.staging.devdrupal.org/ yesterday, edited the group node once, now I noticed this page says "Member since 1 day 21 hours ago" https://localize-7.staging.devdrupal.org/group/node/526/admin/people?sta..., I am sure that I have been around years. So, something in the code re-set this data, maybe it was related to the staging environment.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | issue-seems-still-persist.png | 107.64 KB | baluertl |
| #3 | Screen Shot 2015-07-24 at 18.59.41.jpg | 72.28 KB | baluertl |
Comments
Comment #1
skyredwangComment #2
gábor hojtsyHm, so that is your membership within the team, not on the site. Still strange... I checked Hungarian and Catalan. I did edit Hungarian first and seen their admin is also 2 days 18h, I did not edit Catalan and their admin is also 2 days 18h, so looks like this is something reset only for group admins in the migration. So does not look widespread definitely.
Comment #3
baluertlIf it helps even the tiniest bit, the correct value still appears on the person's profile, even if watching for themselves (see screenshot with admin and simple user), and even if watching someone else's profile.
Comment #4
gábor hojtsyRight, so the data we are talking about here is the group membership date not the site membership date.
Comment #5
japerryThis should be fixed now. Give it a test on staging.
Comment #6
baluertlI'm afraid it's yet still not really the result we want. Or is any caching involved maybe?
Comment #7
gábor hojtsyNot yet resolved :/
Comment #8
japerrySo it looks like group node owners aren't being assigned the correct mapping. Instead of spending time on this, I think I'll just update the created times manually. There are only 142 of them.
Also marking this as a post-launch item, postponed until after launch.
Comment #9
japerryFigured out an easy way to make this happen. It should be fixed now on localize-7.