Tickets :: [#14449] Bug when calling test.php?app=ingo

6.0.0-alpha12

6/12/25

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

08/25/2016 02:31:38 PM	Michael Rubinsky	Comment #8	Reply to this comment
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. Correct.

08/25/2016 02:25:47 PM	webmaster (at) object (dot) earth	Comment #7	Reply to this comment
You didn't say there was any failures in the test script, only that there was an error in the log file. The test script fails with an exception in the frontend at first call of https://webmail.domain.tld/test.php?app=ingo 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. I understand that the test script's purpose is to check a freshly, 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.

08/24/2016 12:53:57 PM	Michael Rubinsky	Comment #6	Reply to this comment
On the other hand, since it is a testing script, it shouldn't return 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. The test script is designed to ensure all dependencies/requirements 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.

08/24/2016 07:32:40 AM	webmaster (at) object (dot) earth	Comment #5	Reply to this comment
On the other hand, since it is a testing script, it shouldn't return 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.

08/23/2016 07:37:44 PM	Michael Rubinsky	Comment #4 State ⇒ Not A Bug	Reply to this comment
Yes, that's not going to work if not authenticated, as it is 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.

08/23/2016 04:33:51 PM	webmaster (at) object (dot) earth	Comment #3 New Attachment: hooks.local.php	Reply to this comment
It is inside: ingo/config/hooks.local.php Which is manually adjusted. I attached the file.

08/23/2016 02:23:25 PM	Michael Rubinsky	Comment #2 State ⇒ Feedback	Reply to this comment
[Show Quoted Text - 11 lines][Hide Quoted Text] In response to: 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'); ...and what file is this line in?

08/23/2016 01:53:40 PM	webmaster (at) object (dot) earth	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Bug when calling test.php?app=ingo Queue ⇒ Ingo Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
In response to: 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.