[Tickets #14121] Administration/Configuration throws error: Call to a member function hasChildNodes() on a non-object in ${INSTALL_PATH}/Horde/Config.php on line 203
noreply at bugs.horde.org
noreply at bugs.horde.org
Wed Sep 30 08:15:14 UTC 2015
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/14121
------------------------------------------------------------------------------
Ticket | 14121
Created By | robert.kovacs.it at gmail.com
Summary | Administration/Configuration throws error: Call to a
| member function hasChildNodes() on a non-object in
| ${INSTALL_PATH}/Horde/Config.php on line 203
Queue | Horde Base
Version | FRAMEWORK_5_2
Type | Bug
State | Unconfirmed
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
robert.kovacs.it at gmail.com (2015-09-30 08:15) wrote:
I am trying to use Horde Groupware 5.2.10 on RH 6.6.
I install a separate pear for horde into ${MYDIR}/horde
I install Horde to the same location, run all the necessary scripts, etc.
When I try to configure horde via ${MYURL}/horde/admin/config (the
link that Administration/Configuration takes me to), I get an error on
the page:
CRITICAL ERROR: Registry could not be initialized from any value
I also get the 'non-object' error described in the summary in syslog.
If I manually rewrite the URL to
${MYURL}/horde/admin/config/config.php?app=${APP}, then it works
except save/etc. links that try to take me back to the non-working
URL, where I have to manually rewrite again to make them work.
I also see the 'CRITICAL ERROR' when a user tries to log in to horde,
but when refreshing the page after the error, the expected things show
up and the login is fine.
The issue is present if I restore my old horde DB contents, as well as
when I start with a clean mysql DB for horde. I also upgraded pear
with 'pear upgrade pear', no changes.
This issue seems to be there since old versions (>=5.1.x ?).
I see people having the same issue in the past, e.g. in #12251
That ticket says the issue was resolved, but does not give any details
about how.
More information about the bugs
mailing list