Re: Midcom-2.2 to 2.4 upgrade

Torben Nehmer <[email protected]>
Newsgroups gmane.comp.web.midgard.user
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Marcelo N. Halpern wrote on 2005-06-28 21:17:
> Thanks Torben. I'm guessing this is becoming a FAQ now. My problem was 
> that midcom-template was not updating correctly. I also noticed that 
> autoconf.php is not packaged with Midcom-2.4.x. I pulled it from CVS 
> and created /etc/midgard/midcom.conf.

Thanks for this hint. It was missing in the makedist script. I have fixed this
and a 2.4.1-1 tarball is underway.


> I ran into another issue though: After successfully upgrading to Midcom 
> 2.4 (tried 2.4.0 and 2.4.1) apache locks up midcom-enabled hosts: cpu 
> utilization runs to 100%. The only messages I get when the php hits 
> memory_limit(128M) or max_execution_time(10m).
> 
> This happens at random and once it begins I have to stop apache, remove 
> all cache files and start it again. I enabled midcom debugging and this 
> is what I see:
> 
> Jun 28 15:07:35 [debug] midcom_helper__basicnav::_is_object_visible: The 
> object ae1203dad4d2cab289db6062ee3970eb (node) is hidden by a viewer 
> group setting.
> Jun 28 15:07:35 [info] _basicnav::constructor: The current node is 
> hidden behind a undecendable one.
> Jun 28 15:07:35 [debug] _basicnav::constructor: Activating last good 
> node (-1) as current node
> Jun 28 15:07:35 [error] _basicnav::_loadNode: Node -1 is not in the 
> MidCOM content tree 8. Aborting
> 
> [...]
>
> with the last two lines repeating ad nauseum. Any ideas what could be 
> wrong? I've gone back to midcom-2.2.2 for now.

Actually, the lines above are the real problem:

MidCOM appearantly tries to load the root node but NAP determines that it is
hidden due to ViewerGroups (line 1). MidCOM then tries to traverse upwards to
find a visible node (lines 2 and 3). Since the root node is invisible, this
fails and is not correctly treated at that point (this is the bug), as it does
detect that the node -1 is not accessible, but won't treat it correctly as it
just continues running instead of triggering an access denied error.

See this bug: http://midcom.tigris.org/issues/show_bug.cgi?id=248

2.4.1-1 should fix this too in that it now shows an error message in these cases.


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[email protected]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCwkMqJPh4Kn6d5FYRArSsAJwIYs59C5mffsn2ZweUcktny8suggCeOSup
w/0kpfge6aso1dlG+4d2TRs=
=uCKp
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.