Resources are set when you return something out of your _init<MethodName>. For example when you use the following source code and return the $_logger, Zend_Application stores the returned value in a registry inside the application.

// place in your bootstrap file.
public function _initLogger()
{
    $writer = new Zend_Log_Writer_Firebug();
    $_logger = new Zend_Log($writer);
    return $_logger;
}

Now the way you get access to the logger is by doing the following inside your controller or controller helper:

class IndexController extends Zend_Controller_Action
{
    public function indexAction()
    {
        // action body
        $logger = $this->getInvokeArg('bootstrap')
                        ->getResource('logger');
    }
}

The key is the getResource() method. You pass in the part following the _init from your method name. This will return the instance of what ever object was returned in the _init method.

Where I got stuck, was since I’m using the Module Bootstrap for my modules and I only want the logger on specific modules and not the whole application when I used the above code it returned null. The reason for null was because it was not in the global bootstrap file. To get access to the resources from the module bootstrap you need to use the following code:

class Admin_IndexController extends Zend_Controller_Action
{
    public function indexAction()
    {
        // action body
        $logger = $this->getInvokeArg('bootstrap')
                        ->getResource('modules')
                        ->offsetGet($this->getRequest()->getModuleName())
                        ->getResource('logger');
    }
}

I hope this helps someone else out there as it was an eye opener to me when I was told about it via the ZF mailing list.

I’ve come up with the following Zend_Filer_Interface so that way you can plug it into anything that has the ability to use Zend_Filter.

Read More for the source code.

Updated on 12/10/09 to include more characters and remove the html version

Updated again on 12/10/09 to make it work with UTF-8 Submitted Forms. I’ve spent half the day validaing this and testing it with a HEX editor

<?php

class Util_Filter_WordChars implements Zend_Filter_Interface
{
    /**
     * Filter out the invalid characters that word puts in.
     * @param string $value
     * @return string
     */
    public function filter($value)
    {

        $search = array(chr(0xe2) . chr(0x80) . chr(0x98),  // '
            chr(0xe2) . chr(0x80) . chr(0x99),  // '
            chr(0xe2) . chr(0x80) . chr(0x9c),  // "
            chr(0xe2) . chr(0x80) . chr(0x9d),  // "
            chr(0xe2) . chr(0x80) . chr(0x93),  // em dash
            chr(0xe2) . chr(0x80) . chr(0x94),  // en dash
            chr(0xe2) . chr(0x80) . chr(0xa6)); // ...

        $replace = array(
            '\'',
            '\'',
            '"',
            '"',
            '-',
            '-',
            '...');

        return str_replace($search, $replace, $value);
    }
}

This could be changed to put them in the html ascii code to display them but I like the standard single quote and double quote online.

Zend_Twitter_Service is currently in the standard trunk for Zend Framework and is scheduled to be released with 1.7.  Please check it out and check back for some examples in the next few days.