| Summary | Filter rules cannot be created with SQL storage backend |
| Queue | Ingo |
| Queue Version | HEAD |
| Type | Bug |
| State | No Feedback |
| Priority | 2. Medium |
| Owners | jan (at) horde (dot) org |
| Requester | dgehl (at) inverse (dot) ca |
| Created | 10/13/06 (7118 days ago) |
| Due | |
| Updated | 4/22/14 (4370 days ago) |
| Assigned | 4/25/07 (6924 days ago) |
| Resolved | 5/21/07 (6898 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
denominator with the people from
ticket 4370that might cause this?State ⇒ Feedback
ticket #4370.State ⇒ Assigned
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Queue ⇒ Ingo
Summary ⇒ fitler rules cannot be created with SQL storage backend
Type ⇒ Bug
backend), the user receives a message that the rule has been created
successfully but this rule is not show in the interface and is also
not saved in the database.
The log file does not show any SQL error message.
I noticed that in the _store function in Storage/sql.php,
case INGO_STORAGE_ACTION_FILTERS:
$ret = true;
break;