remove requirements hook - it's confusing and redundant
Blessed_Steve - October 24, 2007 - 15:41
| Project: | Omniture Integration |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
opened as new bug... taken from http://drupal.org/node/182201
3) admin/logs/status show the module as "Not Configured" (see attachment).
#1
While the error message gives false positives, does that seem useful to you?
My impression is that if there is a configuration problem people will know right away because their reports have no data.
My preference is to remove that whole system and if you agree then I'll go forward with it.
#2
I see what you mean, it is very simple to launch the debugger or a packet sniffer to validate that all systems are go.
I agree that this is an unnecessary feature.
#3
Great, removed it.
#4
Automatically closed -- issue fixed for two weeks with no activity.