<?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>Configuration tabs missing / messed up</title> 
  <pubDate>Fri, 10 Apr 2026 17:02:23 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6762</link> 
  <atom:link rel="self" type="application/rss+xml" title="Configuration tabs missing / messed up" href="https://bugs.horde.org/ticket/6762/rss" /> 
  <description>Configuration tabs missing / messed up</description> 
 
   
   
  <item> 
   <title>This is a fresh install, only the *.php.dist files were rena</title> 
   <description>This is a fresh install, only the *.php.dist files were renamed to *.php. When I go to &quot;Administration -&gt; Configuration&quot;, only some of the tabs are shown and the options shown are often in the wrong place, that is, they should be in another tab (see attached screenshot).</description> 
   <pubDate>Mon, 26 May 2008 19:37:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6762#t45620</link> 
  </item> 
   
  <item> 
   <title>Check if your config/conf.xml file is broken. And did you up</title> 
   <description>Check if your config/conf.xml file is broken. And did you upgrade from an earlier version?</description> 
   <pubDate>Mon, 26 May 2008 20:38:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6762#t45621</link> 
  </item> 
   
  <item> 
   <title>The config/conf.xml is fine (fresh install, no previous vers</title> 
   <description>The config/conf.xml is fine (fresh install, no previous version). I noticed a couple of other things:

- the same error occurs with Horde 3.1

- the error does not occur on another server with almost exactly the same setup: PHP 5.2.6 on Gentoo Linux, compiled against the same libxml, etc. 



The only difference is that the server where it works is running mod_php and the server that produces the error is running php as fcgi. Could that be a lead? I raised the log-level, but no information is logged when I open the configuration. The weird thing is that all applications (IMP, Kronolith, etc.) work fine. That&#039;s also the reason why I only noticed it now when I prepared upgrading to the new stable release. I hadn&#039;t touched the running configuration in a long time...

</description> 
   <pubDate>Mon, 26 May 2008 21:26:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6762#t45622</link> 
  </item> 
   
  <item> 
   <title>Definitely sounds like a problem with the DOM extension. Can</title> 
   <description>Definitely sounds like a problem with the DOM extension. Can you play around with doing basic xml parsing on the two installs?</description> 
   <pubDate>Mon, 26 May 2008 21:46:51 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6762#t45623</link> 
  </item> 
   
  <item> 
   <title>&gt; Definitely sounds like a problem with the DOM extension. C</title> 
   <description>&gt; Definitely sounds like a problem with the DOM extension. Can you play 

&gt; around with doing basic xml parsing on the two installs?



I did and I found a workaround. In lib/Horde/Config.php on line 547, I changed md5(microtime()) to md5(rand()) and it seems to work now (I don&#039;t know if replacing the other occurrences of microtime() is necessary).



The server is a dual-core machine with thread support for PHP and Apache using mpm-worker. So, I&#039;m wondering if it&#039;s possible that microtime() actually returns the same time more than once...</description> 
   <pubDate>Mon, 26 May 2008 23:53:48 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6762#t45624</link> 
  </item> 
   
  <item> 
   <title>Ah, not xml then - nice find. This should fix it too then:

</title> 
   <description>Ah, not xml then - nice find. This should fix it too then:

http://lists.horde.org/archives/cvs/Week-of-Mon-20080526/079006.html</description> 
   <pubDate>Tue, 27 May 2008 02:13:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6762#t45626</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
