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 made a useless patch for my local installation to track what users are doing in the localization server. It could be useful for little localization servers, i'm conscius that this patch can't applied to a centralized server as is.
| Comment | File | Size | Author |
|---|---|---|---|
| l10n_community.module.patch | 968 bytes | psicomante | |
| pages.inc_.patch | 982 bytes | psicomante |
Comments
Comment #1
psicomante commentedI missed to patch import.inc
Comment #2
gábor hojtsyThe project info might be misleading (as strings are shared among projects), but at the same time could be useful for logging purposes (as we know where was the string added, and we might get more information about motivations behind adding that string).
However, I don't think watchdog logging of this is a good idea. We have every piece of data on new strings in the database already, and you could do simple queries on the tables, monitoring any user activity back to the start when the site was set up. The originating user is recorded, submission time and user is recorded, etc. I don't think it is a good idea to misuse the watchdog system with this.
Comment #3
psicomante commentedI was thinking about tracking user activity. How can do this without patching the module?
Comment #4
gábor hojtsyWhat kind of tracking? Why do you reply to this issue? The watchdog() messages are insufficient?