Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
views.module
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Issue tags:
Reporter:
Anonymous (not verified)
Created:
29 Nov 2012 at 02:09 UTC
Updated:
19 Jul 2025 at 04:39 UTC
Jump to comment: Most recent
Comments
Comment #0.0
xjmUpdated issue summary.
Comment #0.1
xjmUpdated issue summary.
Comment #1
xjmComment #2
xjmdblog has also come up several times, so we might want to add integration for that as well.
Comment #3
pounardWatchdog is pluggable and this integration would work only with the dblog module, which may end up being useless for a lot of big-sized sites which will prefer either disabling it, either using a more performant or custom logging solution.
Comment #4
catchAt #3, that doesn't stop the dblog module providing its own views integration, if you switch off dblog module then the views integration goes with it.
Where it does get trickier is with #1289536: Switch Watchdog to a PSR-3 logging framework or any other system where hook_watchdog() moves to a pluggable class.
Comment #5
dawehnerIf someone wants to implement dblog views integration, please try to do something else.
I have a bunch of people which could help with that and maybe the other views integration issues.
Comment #6
xjmWe noticed today that Forum has a denormalized
{forum_index}table, and it could make sense to introduce integration for that table rather than joining across to Node and Taxonomy and so on.Out of scope, but I have the vague notion that core could use some generalized solution for these index tables, for query abstraction and so on.
Comment #6.0
xjm.
Comment #6.1
xjmUpdated issue summary.
Comment #6.2
xjmUpdated issue summary.
Comment #7
catch@xjm the generalized abstraction is http://drupal.org/project/mv it's been around for years and no-one's ever tried to get it into core (or even a stable contrib release), it is needed though yes.
Comment #7.0
catchadd forum issue in
Comment #8
klonosI was pointed to this issue from #1972282: 'Missing handler: node created_year_month argument', but this is a META with a lot of children issues. I have no way to tell which commit from the issues mentioned in the summary could have caused it (if it actually did) and it might be a duplicate of another issue already filed.
Does anyone have a clue?
Comment #8.0
klonosadd dblog
Comment #8.1
xjmRemoving myself from the author field so I can unfollow. --xjm
Comment #8.2
jhodgdonadd link to related issue
Comment #8.3
klonos...put issues in chronological order.
Comment #9
frobIs this issue still necessary or now that we are on the minor release cycle can we just evaluate each of these on their own?
Comment #10
jhodgdonWe normally leave Meta issues open until all child issues have been resolved. This one still has several open children.
Comment #19
pasqualleComment #24
quietone commentedOnly two more issue to complete!
Comment #25
xjmAw, poor Locale.
Given that there is now only one open child issue (the other was wontfixed) and that the scope was limited to a set of Drupal 7 default views descoped from the module before we added it to core, I'm going to go ahead and mark this meta fixed. The poor Locale view can march bravely onward by itself. 🥲