Jeroen Keppens : Zend_Tool : Action 'show' is not a valid action.

2009-07-03 19:49

Zend_Tool : Action 'show' is not a valid action.

Sometimes you can get a head-ache looking at those stupid little things that make your app go gaga.

Tonight I made a fresh install of my Zend Library (upgrade to 1.8.4) and I decided to keep a copy of the full 1.8.4 directory and put a symbolic link to the Zend library in the include path. I copied the zf* files to my /usr/local/bin (and made symlink zf) and tried it out:

dev:/var/www/Test# zf show version
An Error Has Occurred
Action 'show' is not a valid action. 

Zend Framework Command Line Console Tool v1.8.4
Usage:
    zf [--global-opts] action-name [--action-opts] provider-name [--provider-opts] [provider parameters ...]
    Note: You may use "?" in any place of the above usage string to ask for more specific help information.
    Example: "zf ? version" will list all available actions for the version provider.

Providers and their actions:

After some testing and googling, I found out that Zend_Tool didn't like the Zend folder to be a symlink instead of a hard copy. So, copying the Zend directory to the include path instead of linking it did the trick:

dev:/var/www/Test# zf show version
Zend Framework Version: 1.8.4

I hope this post helps you before you get a head-ache.

jim

2009-07-10 21:31

Jeroen, Thanks for all your work and sharing. Your approach to ZF modules has helped me greatly. Here's how I set up my ZF library using symlinks.

copy ZF tarball to /somepath/somedirectory
cd /somepath/somedirectory
untar ZF tarball (for this example I'll use version 1.8.4)

ln -s ./ZendFramework-1.8.4/ zf-1.8.4
ln -s ./zf-1.8.4/ zf-latest

rather than copy the zf.sh files to /usr/local/bin I create a symlink.

cd /usr/local/bin
ln -s /somepath/somedirectory/zf-latest/bin/zf.sh zf

I use /somepath/somedirectory/zf-latest/library in my include_path.

zf works. This probably works for me because I do not move the zf files from their original location. Using a symlink in your include_path is probably not the reason for your head-ache.

When I change to another release of ZF, as long as the zf-latest symlink is pointing to the right location then /usr/local/bin/zf and the include_path are using the latest released versions without having to make any changes.

Keep up the good work.