Is this a stock eZ Publish 3.9.2 installation or a customized build of eZ?
Trying to understand what might be unique in your environment which may play a part in the problem. I do know that php 4.4.2 does have some problems which is why php 4.4.7 is recommended these days ...
I knew I forgot something. This is a stock 3.8.6 eZ install. I'll see about up grading php. I don't think that php version is in the the dapper repositories, but I may be able to find it elsewhere.
How do you know that apache is segfaulting? Are there any error messages in the apache logs?
Have you tried it with debugging on? What happens if you incrment the depth parameter e.g. $image.data_map|attribute(show,2), $image.data_map|attribute(show,3) etc at what value does it stop working?
You might find that the system is simply running out of memory or reaching a timeout limit in retrieving all the information to the default depth (I think it's 5) - I take it that it's running OK apart from this issue?
Yeah, I'm getting Segfault (11) in my apache error logs when I get a zero response from the server.
So far {$image.data_map.image|attribute(show,1)} is where I've isolated the problem. But like I said before I can get to $image.data_map.image.content|attribute(show,1).
Fortunately I'm able to work around this little problem and get my template done. And the site is running just great. It's just a little weird. It very well could be my PHP version. But it looks like I'll have to compile a new version since I can't find 4.4.7 in a Dapper repository.
--Andrew
You must be logged in to post messages in this topic!
