Summary | Setting hashtable prefix from GUI when using php 5.4 causes horde to not start |
Queue | Horde Base |
Queue Version | 5.1.5 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | it (at) wenn (dot) com |
Created | 12/18/2013 (4218 days ago) |
Due | |
Updated | 12/18/2013 (4218 days ago) |
Assigned | |
Resolved | 12/18/2013 (4218 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | Yes |
expressions but without it anyone migrating from 5.3 to 5.4 with a
simple prefix will break the system. Mabey there is a better way
around this.
which implies that you do not need too and herin lies the problem, im
sure that many have not entered any expression in and now they will
see a problem when they upgrade to 5.4 and nothing works, only trial
and error will find the problem in the config file.
State ⇒ Not A Bug
Priority ⇒ 1. Low
expressions but without it anyone migrating from 5.3 to 5.4 with a
simple prefix will break the system. Mabey there is a better way
around this.
expressions but without it anyone migrating from 5.3 to 5.4 with a
simple prefix will break the system. Mabey there is a better way
around this.
New Attachment: hashtable_prefix_fix.patch
entered data in the conf.php file.
In PHP 5.3 this was not a problem but since we upgraded to PHP 5.4
horde will no longer startup, it just uses all the available memory
until script stops.
If I manually put quotes around the prefix either in the GUI or
directly in the file then Horde starts fine.
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Setting hashtable prefix from GUI when using php 5.4 causes horde to not start
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ Yes
State ⇒ Unconfirmed
entered data in the conf.php file.
In PHP 5.3 this was not a problem but since we upgraded to PHP 5.4
horde will no longer startup, it just uses all the available memory
until script stops.
If I manually put quotes around the prefix either in the GUI or
directly in the file then Horde starts fine.