Glad to hear you were able to solve your own problem.

On my end, I’ve further updated VuFind to better integrate some of the new Zend\Console features — specifically, I have replaced echo calls with \Zend\Console\Console::writeLine(), and I have replaced exit() calls with return $this->getResponse()->setErrorLevel() calls. The relevant diffs are here:

http://vufind.git.sourceforge.net/git/gitweb.cgi?p=vufind/vufind;a=commitdiff;h=3108e046d043db4ec1829d589410925bea2677a7

I still need to think about whether to replace my custom routing solution with the new built-in console router. For the moment, I’m still using my custom router in combination with the old \Zend\Console\Getopt parameter processing.

Based on a bit of investigation, I don’t think I can easily incorporate the new router with my “individual PHP files for individual actions” approach. The best way to move forward without creating nasty hacks would probably be to replace all the individual PHP files with shell scripts and batch files that call index.php with the relevant action/controller parameters concatenated with user input. This may technically be a better solution than what we currently have, but it would break backward compatibility (i.e. people would need to change their existing automation to call scripts instead of execute PHP) and it would clutter up the directories (since cross-platform compatibility would require both batch files and shell scripts for every single action). For now, it’s a backburner item.

http://packages.zendframework.com/docs/latest/manual/en/modules/zend.console.controllers.html

The use of the zf command confused me though since it’s been removed while they refactor it. It took me a while to figure out calling the index.php file after creating a console route was what I needed.

If you do update your code for the new Zend Console stuff, I’d like to see how it’s done. There’s basically zero documentation for it and I’m having a hard time figuring out how to create a cli script.

Since I don’t currently have time to fully investigate the new capabilities, I have put in some workarounds to allow my existing solution to continue functioning — it just amounts to moving some logic from the CLI module’s bootstrap callback into a custom router, and skipping a few other bootstrap routines when running in console mode.

Here are the Git commits in case you are interested:

http://vufind.git.sourceforge.net/git/gitweb.cgi?p=vufind/vufind;a=commitdiff;h=cd85deb6c2984aa6ac56a76879230e7397fe4af5

http://vufind.git.sourceforge.net/git/gitweb.cgi?p=vufind/vufind;a=commitdiff;h=a30f235ca61c278fb3a883e11c65c522007f0b43

However, this is just a temporary solution. I need to come up with something that’s better integrated with the framework. I’ll work on that later after some higher priority refactoring is done, and I’ll try to post something here if the subject isn’t better-documented elsewhere by that time.