| Summary | Ingo H4 doesn't appear to read from backends.local.php |
| Queue | Ingo |
| Queue Version | 2.0.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | budic (at) onholyground (dot) com |
| Created | 04/21/2011 (5315 days ago) |
| Due | |
| Updated | 05/04/2011 (5302 days ago) |
| Assigned | 04/21/2011 (5315 days ago) |
| Resolved | 05/04/2011 (5302 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
default. Definitely not a bug, but perhaps the documentation in that
file could be clearer. Let me know how should I submit suggested
improvements, and I'll see what I can come up with that explains it
better.
State ⇒ Not A Bug
New Attachment: backends.local.php
in backends.local.php or forgot the leading "<?php"?
backends.local.php isn't being read on my system. If I replace
backends.php with my backends.local.php, ingo works fine. If the
default backends.php is in place (and I'm using backends.local.php), I
don't have any sieve rules available (spam, vacation, etc).
I've attached my file if you want to take a look. My backends.php is
the default that shipped with ingo when I installed 2.0.0. Same issue
after upgrading to 2.0.1.
State ⇒ Feedback
backends.local.php or forgot the leading "<?php"?
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Ingo H4 doesn't appear to read from backends.local.php
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
backends.local.php, when I moved them to backends.php, they worked.