Zitat von Hiromi Kimura <hir...@tac.tsukuba.ac.jp>:

From: Michael M Slusarz <slus...@horde.org>
Subject: Re: [imp] Search "entire message" member function fetch() on a non-object
Date: Thu, 12 Jun 2014 01:21:50 -0600

Quoting Samuel Wolf <sam...@sheepflock.de>:

Zitat von Michael M Slusarz <slus...@horde.org>:

Quoting Samuel Wolf <sam...@sheepflock.de>:

Hi,

at the moment I use IMP-6.2.0beta1* with Horde-5.2.0beta2 and
Horde_Core-2.12.0beta2 since there are some bugs which affect me in
IMP-6.2.0beta2.

One of my user can search in the INBOX with "entire message", get the
search result and can open the message in the preview mode.
Same user can search in the "Sent" folder with "entire message", get
the search result but after select a message or double click on it
Horde show "Error when communicating with the server.".

Horde.log:
2014-06-07T13:53:02+00:00 EMERG: HORDE [imp] Call to a member function
fetch() on a non-object [pid 17325 on line 1616 of
"/var/www/http/horde/imp/lib/Contents.php"]

POST https://example.com/horde/services/ajax.php/imp/showMessage
[HTTP/1.0 500 Internal Server Error 297ms]
"onFailure" {request: Object, transport: XMLHttpRequest, readyState:
4, status: 500, statusText: "Internal Server Error", responseText:
"<html>
<head><title>Horde :: Fatal Error</title></head>
<body style="background:#fff; color:#000"><h1>A fatal error has
occurred</h1><h3>Call to a member function fetch() on a
non-object</h3><h3>Details have been logged for the
administrator.</h3></body></html>", headerJSON: null, responseXML:
null, responseJSON: null}

It works sometimes in sent, but do not found the logic when it works
an when not. :(

Any ideas?

Absolutely no clue.  There are only two outcomes to calling fetch() -
it returns a Results object or it throws an Exception.  Neither could
produce this error message.  You will need to debug locally.

Michael, help this to track the issue down?

Maybe it's this (?)

https://github.com/horde/horde/commit/531dd6eb2ae6a71ed627fe92807a494c4a841d5f

Sorry, I installed from Git and got same result.

I revert some old tar-ball of installation which installed from Git.
8th April (GMT+9) version is OK,
10th April version and later have this issue.

Is it possible for you to find the commit which cause the issue?
Unfortunately I'm not on git.



I can't reproduce.

michael

___________________________________
Michael Slusarz [slus...@horde.org]

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org


-=-=-=-=-
Hiromi Kimura, Tandem Accelerator Complex, University of Tsukuba, JAPAN

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org



--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org

Reply via email to