zg:zeitgeist
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
zg:zeitgeist [2006/04/08 21:06] – fgm | zg:zeitgeist [2020/11/23 17:23] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 8: | Line 8: | ||
===== Features ===== | ===== Features ===== | ||
- | |||
- | |||
- | |||
==== Current ==== | ==== Current ==== | ||
* Log searches with their timestamp | * Log searches with their timestamp | ||
- | * A customizable | + | * A themable |
- | * A customizable | + | * A themable |
- | * 4.7RC2 compatible. | + | * A page displaying the most requested searches over a given time span |
- | + | * 4.7.4 to 7.x compatible. | |
- | + | ||
==== Wishlist ==== | ==== Wishlist ==== | ||
- | * A page displaying the most requested searches over a given time span | ||
* A RSS feed tracking all searches | * A RSS feed tracking all searches | ||
* A periodic (weekly) summary of the top queries, by email to the site admin | * A periodic (weekly) summary of the top queries, by email to the site admin | ||
* A setting to include queries by UID=1 or not | * A setting to include queries by UID=1 or not | ||
- | * make the customizable blocks themeable, not just customizable | + | * Export |
+ | * Empty the current table | ||
Looking further: | Looking further: | ||
- | * ability to log various site uses, instead of just searches. | + | * ability to log various site uses, instead of just searches |
* coupling with statistics.module | * coupling with statistics.module | ||
+ | * a cleaner way of trapping queries (why not just hook_search ?) | ||
===== Data ===== | ===== Data ===== | ||
- | + | ||
* Table ' | * Table ' | ||
* Variables: | * Variables: | ||
Line 46: | Line 42: | ||
===== Recurring issue ===== | ===== Recurring issue ===== | ||
- | As of 4.7, Drupal does not implement a standard logging API, be it for search or anything else. The net result is that code like zeitgeist.module, | + | As of 4.7.x/7.x, Drupal does not implement a standard |
+ | |||
+ | * The core patch from which this module has been born used to parse the standard " | ||
+ | * For zeitgeist.module 4.7.x-1.1 to 4.7.x-1.6, this meant parsing both the " | ||
+ | * Later versions only alter search forms to add a submit handler. This simplifies the code, but leave it vulnerable to search.module changes. | ||
+ | |||
+ | At some point, drupal core will probably evolve to include such a logging mechanism, and zeitgeist will then be able to use it. Should the module become popular, it is also conceivable that search.module add a recording hook, independent of other recording needs. Things have evolved for the better in Drupal 7, where a single form implementation is used for all search forms, allowing simpler and more generic logging from the form submit handler. | ||
+ | |||
+ | Until this happens, it could be possible to use [[http:// | ||
+ | |||
+ | - rename drupal' | ||
+ | - implement a local do_search() function in zeitgeist.module. At this point calls by other modules should go to the new function instead of the standard version | ||
+ | - within this local do_search, | ||
+ | - perform the _zeitgeist_store_search | ||
+ | - invoke the standard do_search, now called zeitgeist_do_search | ||
+ | - return the results obtained from the standard do_search from our custom do_search | ||
+ | |||
+ | Problems: | ||
- | * The core patch from which this module has been born used to parse the standard | + | * This would fail if the standard |
- | * For zeitgeist.module 1.1 to 1.6, this meant parsing both the "search form" | + | * This requires |
- | * Version 1.7 only processes the " | + | |
- | At some point, drupal core will probably evolve to include such a logging mechanism, and zeitgeist will then be able to use it. Should the module become popular, it is also conceivable that search.module add a recording hook, independent of other recording needs. |
zg/zeitgeist.1144530401.txt.gz · Last modified: 2020/11/23 17:23 (external edit)