[Tickets #12410] Re: After upgrading to 3.1.1 from 3.0.x Ingo fails to display Sieve Rules

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12410
------------------------------------------------------------------------------
  Ticket             | 12410
  Updated By         | christoph.haas at ukbw.de
  Summary            | After upgrading to 3.1.1 from 3.0.x Ingo fails to
                     | display Sieve Rules
  Queue              | Ingo
  Version            | 3.1.1
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


christoph.haas at ukbw.de (2013-10-11 08:33) wrote:

I've restarted my Apache2 severeal times, but the error did not go away!

If I insert "print_r($scripts)"  before line 116 in  
"/var/www/horde/ingo/lib/Factory/Script.php" as suggested, so it reads
--- snip ---
public function createAll()
     {
         $scripts = $GLOBALS['session']
             ->get('ingo', 'backend/script', Horde_Session::TYPE_ARRAY);
         $instances = array();
         /* 2013-10-11, 10:04:36, haasc: fuer debugging */
         print_r($scripts)
         foreach (array_keys($scripts) as $rule) {
             $instances[$rule] = $this->create($rule);
         }
         return $instances;
     }
--- snap ---

and reload the page, the whole Horde-WebUI (not only Ingo!) wents just white.
No error in "var/log/syslog", no error in "/var/log/apache2/error.log" ...

After removing or commenting the "print_r($scripts)"-line, everything  
is again OK besides that no sieve-filters are displayed in Ingo.

Where can I look further?

System Debian, Horde 5.1.2. Ingo 3.1.2.
The Mailserver resides on different machine.
I have several sieve-scripts, which I can manage on the mailserver via  
sievshell, so that it is verfied that timsieved is working.