<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Setting hashtable prefix from GUI when using php 5.4 causes horde to not start</title> 
  <pubDate>Fri, 10 Apr 2026 14:37:17 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/12883</link> 
  <atom:link rel="self" type="application/rss+xml" title="Setting hashtable prefix from GUI when using php 5.4 causes horde to not start" href="https://bugs.horde.org/ticket/12883/rss" /> 
  <description>Setting hashtable prefix from GUI when using php 5.4 causes horde to not start</description> 
 
   
   
  <item> 
   <title>When setting the hashtable prefix via the GUI seems to not q</title> 
   <description>When setting the hashtable prefix via the GUI seems to not quote the 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.</description> 
   <pubDate>Wed, 18 Dec 2013 12:43:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12883#t81894</link> 
  </item> 
   
  <item> 
   <title>&gt; When setting the hashtable prefix via the GUI seems to not</title> 
   <description>&gt; When setting the hashtable prefix via the GUI seems to not quote the 
&gt; entered data in the conf.php file.
&gt; In PHP 5.3 this was not a problem but since we upgraded to PHP 5.4 
&gt; horde will no longer startup, it just uses all the available memory 
&gt; until script stops.
&gt; If I manually put quotes around the prefix either in the GUI or 
&gt; directly in the file then Horde starts fine.
</description> 
   <pubDate>Wed, 18 Dec 2013 12:43:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12883#t81895</link> 
  </item> 
   
  <item> 
   <title>Understandably this patch causes an issue with allowing PHP </title> 
   <description>Understandably this patch causes an issue with allowing PHP 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.</description> 
   <pubDate>Wed, 18 Dec 2013 12:52:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12883#t81896</link> 
  </item> 
   
  <item> 
   <title>&gt; Understandably this patch causes an issue with allowing PH</title> 
   <description>&gt; Understandably this patch causes an issue with allowing PHP 
&gt; expressions but without it anyone migrating from 5.3 to 5.4 with a 
&gt; simple prefix will break the system. Mabey there is a better way 
&gt; around this.
Yes. Enter a PHP expression like the instruction says.</description> 
   <pubDate>Wed, 18 Dec 2013 13:24:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12883#t81897</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; Understandably this patch causes an issue with allowing P</title> 
   <description>&gt;&gt; Understandably this patch causes an issue with allowing PHP
&gt;&gt; expressions but without it anyone migrating from 5.3 to 5.4 with a
&gt;&gt; simple prefix will break the system. Mabey there is a better way
&gt;&gt; around this.
&gt; Yes. Enter a PHP expression like the instruction says.

Does not say that in the instructions, it just says that its allowed 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.</description> 
   <pubDate>Wed, 18 Dec 2013 13:28:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12883#t81898</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
