Tickets :: [#12436] upgrade docs wrong

07/08/2013 12:57:28 PM	jmozdzen (at) nde (dot) ag	Comment #3	Reply to this comment
Those are the upgrade docs for Ingo 2. you're right - but as one reads through this stuff incrementally, especially when re-installing things and noticing that one's sieve server is on the old port, one is tempted to appy that change to the current file. Since that part changed, I highly recommend to add the mentioned new statements to the section concerning the latest upgrade.

07/08/2013 12:53:14 PM	Jan Schneider	Comment #2 State ⇒ Rejected	Reply to this comment
Those are the upgrade docs for Ingo 2.

07/08/2013 11:33:04 AM	jmozdzen (at) nde (dot) ag	Comment #1 Priority ⇒ 1. Low Patch ⇒ Yes Milestone ⇒ Queue ⇒ Ingo Summary ⇒ upgrade docs wrong Type ⇒ Enhancement State ⇒ New	Reply to this comment
In http://www.horde.org/apps/ingo/docs/UPGRADING, 4.2, the code sample given is IMHO wrong: currently: $backends['sieve']['params']['port'] = 2000; $backends['sivtest']['params']['port'] = 2000; IMO should read $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['port'] = 2000; $backends['sieve']['transport'][Ingo::RULE_ALL]['params']['port'] = 2000; due to the configuration changes introduced with latest Ingo.