Draft: updateLastActivity

Closes #1595 (closed)

What does this MR do?

Sets the last_activity correctly even is user is not visiting login or dashboard

How confident are you it won't break things if deployed?

should be reviewed

Links to related issues

#1595 (closed)

How to test

1. Login in test envronment

2. Set users last_activity directly in the database to the past

3. open page region->members without visting login or dashboard and filter for current user

4. past date is shown for last_activity but should be current date

5. Checkout branch locally

6. open page region->members without visting login or dashboard and filter for current user

7. past date shows current date as last_activity correctly

Screenshots (if applicable)

Checklist

• added a test, or explain why one is not needed/possible...
• no unrelated changes
• asked someone for a code review
• set a "for:" label to indicate who will be affected by this change
• added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
• added an entry to CHANGELOG.md
• added a short text that can be used in the release notes
• Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
  • Consider writing a detailed description in German.
  • Describe in a few sentences, what should be tested from a user perspective.
  • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
  • Be aware, that also non technical people should understand.

Release notes text in German

Das Feld Letzte Aktivität wird nun korrekt in der Datenbank gesetzt, auch wenn direkt auf eine Unterseite gesprungen wird, ohne über Login oder Dashboard zu gehen.