Closed (fixed)
Project:
Performance Logging and Monitoring (D7)
Version:
7.x-1.6
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
13 Nov 2012 at 20:30 UTC
Updated:
4 Jan 2014 at 02:42 UTC
Jump to comment: Most recent
Comments
Comment #1
malc0mn commented2 good ones. Best IMHO would be to add a language column and make path & language primary key for the summary table...
Comment #2
mgiffordSounds like that approach would work well. In most cases it would be the same, but not all.
Comment #3
mgiffordWanted to also say that this might be something that could easily wait till D8. At the moment there's no support for this with similar core code like:
/en/admin/reports/page-not-found
Although I encourage modules to be better from core... I'm also totally fine to postpone this.
Comment #4
malc0mn commentedAdded the clickable paths suggestion to both D6&7.
@#2: In what cases would adding a language column not be enough? Can't think of any... I'll just write
to the DB in a separate column? That way you know in what language the URL was called. I pass it on to the l() function and the path will be generated alias and all so you can click it in the overviews.
When using entity translations the node id will stay the same, but the language differs, so making path + language primary key solves that problem as well...?
Comment #5
malc0mn commentedAdded language DB column and logging to 2.x branch (summary & detail), probably won't be backporting this to 1.x version as the 2.x should really replace that with the new #1848850: We don't need different data stores - let Drupal's cache backend decide approach.