[Tickets #10017] Re: applications are incorrectly "polled" even if they are not installed
bugs at horde.org
bugs at horde.org
Mon May 2 19:34:04 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/10017
------------------------------------------------------------------------------
Ticket | 10017
Updated By | Michael Slusarz <slusarz at horde.org>
Summary | applications are incorrectly "polled" even if they are
| not installed
Queue | Horde Framework Packages
Version | Git master
Type | Bug
State | Not A Bug
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
Michael Slusarz <slusarz at horde.org> (2011-05-02 19:34) wrote:
>>> Yeah I could, but this is not consistent between applications. For
>>> example I don't have Ansel installed, and it does not appear in the
>>> logs. At least it should not be logged with ERROR level. INFO should
>>> be more appropriate.
>>
>> If an application is marked as being active, and doesn't exist, that
>> is a big deal and most definitely needs to be marked as an ERROR.
>
> Can you elaborate why this is a big deal?
If code is explicitly trying to access an application that doesn't
exist, it is most likely a configuration file issue. You can't be
hiding configuration file issues in INFO messages - this is exactly
what the logs are useful for. The whole point is you should NOT be
seeing these errors at all (see below).
> Also I still don't see a logic why applications without blocks are
> "silently" ignored at DEBUG level but with blocks fills the log with
> ERRORs?
They don't fill the logs with ERRORs. That's the whole point. These
non-existent applications will be ignored if the application doesn't
exist in your installation.
See Horde_Registry when we parse the registry.php file - when looping
through the list of applications defined as "not inactive" in
registry.php, we do a file_exists() check to see if that application's
directory exists. If it doesn't, we issue a DEBUG message and mark
the application (or block) as inactive. So there is most likely an
issue with your configuration that is causing this check to fail, even
though the applications don't exist.
More information about the bugs
mailing list