Anyone got ANY idea what could be causing an issue with Zend Navigation. My environments are provisioned through chef and are the same OS etc, same apache setups etc. On my local Ubuntu VM, my webapp renders correctly. The SAME code fails to render the navigation on my TEST VM (on AWS). When I say the same, I've checked and double checked (and is all deployed through PHING), including SCPing the no-displaying-correctly-code off TEST back onto my box, where it then works correctly.
I'm totally stuck. Does anyone know any low level quirks about how Zend renders nav? DOes it write to temp files or something (long shot). The issue is a routing one IMO. The menu doesn't think it is active, yet is using the same routes.ini file as my dev environment, where is it fine.
I've tried changing the environment settings (development, testing) etc but nothing. It can't be the DATA as there is no impact on routing.
Really appreciate any insight..
SOLUTION!
Ahh haaaa. The nav appears to have been broken by a revision of Zend. The reason that was not seen locally, is because I am using Vagrant to manage by VM locally. The mounted folder is , of course, a read-ony filesystem, so my "ln -s -f symlink" to the correct vendor of Zend was silently failing in my script, but working on LIVE on AWS - hence they were using different Zend versions and the new release which breaks my nav (!ANother story) was only seen on Live...! Here end-eth the lesson to self. ALWAYS halt-on-failure in your deployment scripts
