Summary | Bug when calling test.php?app=ingo |
Queue | Ingo |
Queue Version | 3.2.11 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | webmaster (at) object (dot) earth |
Created | 08/23/2016 (3215 days ago) |
Due | |
Updated | 08/25/2016 (3213 days ago) |
Assigned | 08/23/2016 (3215 days ago) |
Resolved | 08/23/2016 (3215 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
applied changes to horde modules / configurations, I must test my
changes seperately against the test script environment.
there was an error in the log file.
of https://webmail.domain.tld/test.php?app=ingo
be safe to run in the use case you are describing, YOU need
to perform a test to be sure either there is an active session,
or that the Mail API is available. Either way, not a bug.
unmodified installation to be checked. It is not necessarily capable
to run it's tests smoothly, if I changed something in the system after
installation.
It does not matter, that my changes are valid and correct for
production use. The test script may still fail.
If I want to ensure the test script to work correctly, after I applied
changes to horde modules / configurations, I must test my changes
seperately against the test script environment.
false negatives, because the setup works fine in production.
It took me a while to figure that only the testing script fails, not
the production scenario though.
are met after installation, or in some cases to help identify a
problem you may be seeing during production. You are obviously running
this after you have modified/added your own hook code. You didn't say
there was any failures in the test script, only that there was an
error in the log file. Furthermore, this is YOUR code, not Horde's. If
you want it to be safe to run in the use case you are describing, YOU
need to perform a test to be sure either there is an active session,
or that the Mail API is available. Either way, not a bug.
false negatives, because the setup works fine in production.
It took me a while to figure that only the testing script fails, not
the production scenario though.
State ⇒ Not A Bug
attempting to connect to the mail application. The test page must
initialize the application to perform it's tests. Considering that
this is a test page that shouldn't even be enabled on a production
machine, I would not consider this a bug.
New Attachment: hooks.local.php
Which is manually adjusted.
I attached the file.
State ⇒ Feedback
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Bug when calling test.php?app=ingo
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
https://lists.horde.org/archives/ingo/Week-of-Mon-20160321/002400.html
The issue occurs only when using the test-script that comes with
horde: https://webmail.domain.tld/test.php?app=ingo
The second call of the URL returns no error. After deleting domain
cookies, the next call will produce the error again.
A var_dump shows, that the line:
$ob = $GLOBALS['registry']->call('mail/imapOb');
returns null.
Using the webinterface does not produce this error at all. After
login, the statement above returns the expected object and everything
works just fine.