Currently the only way for Zend_Tool to pick up your custom providers is to add the provider directory to the php include path. This is especially problematic if you have multiple applications in one server.
One workaround I use is to create a script wrapping zf.sh in [APP_ROOT]/script:
ZF_CONFIG_FILE = $(pwd)’/application/configs/zf.ini’
ZEND_TOOL_INCLUDE_PATH_PREPEND = $(pwd)’/providers’
`which zf` $@
If you have integrated the Zend library in your application, you can add the zf scripts in the same folder as the script. The last line then becomes:
Now you can use script/zfc instead of zf and all of your custom providers should get loaded correctly.
From Manuel Lemos of PHPClasses:
The number of Indian PHP developers has been growing at a large pace in the last few years, when compared to other countries. A few years ago, India was just one of the top ten countries with more PHP developers. Now India is number 2 and is almost surpassing United States, which is still number 1.
While it is difficult to take such broad conclusions seriously based on member statistics of a single community, PHPClasses does have a large user base and can arguably be considered representative. Any article tagged India and software these days attract the usual crap about how Indian developers are the worst and how everybody who outsources to India never does it again. So I was surprised when some of the usually ‘silent’ majority of the client base who continue outsourcing development to India came out to defend their decision.
I did come away with a very interesting statistic; Indian developers have won most awards this year for their contribution against sizable competition. Most Indian developers I meet have difficulty understanding the concept of giving back to the community, so it’s always refreshing to see a number of people doing exactly that.
Back when I was actively involved with TYPO3 projects, one item in my wish list was a login box for front end users which would allow granular control over pages where the user is redirected after successful login. Naturally, when Chetan and me got together recently to contribute a suite of plug-ins related to the front end user, this functionality was on the top of my mind.
The login box has some standard features like storage folder for user records, etc. However the redirection options allow much more control than other plug-ins. You can have a global redirection page just like you are used to. However, using Typoscript blocks you can have a different configuration for every individual user if you want. But I suppose the group level controls would be much more used in practice. You only have to add blocks when you want something different since the other settings act as fallbacks if there is nothing set for the current user or group, in that order.
Unlike many other contributions to the TER, this extension is not derived from some commercial work. We wanted to contribute something we wanted for ourselves when we were working with TYPO3. The current release as of the time of writing contains only the login box since we have also tried to create a robust framework for future developments (Chetan was responsible for all the framework related work). In the coming weeks, we have plans to add some very interesting features and plug-ins to the suite.
Extension download and documentation
FE User Suite