Re: [fw-general] Changelog / Recently Resolved
Thanks for that summary. Very much appreciated.
Sincerely, gonyuu
GavinZend wrote:
>
> You can "watch" the JIRA issues, and receive email notification, or you
> can review the Changelog:
>
> http://framework.zend.com/issues/browse/ZF?report=com.atlassian.jira.plugin.system.project:changelog-panel
>
> http://framework.zend.com/wiki/x/cAE - watch using RSS feeds
>
> However, the Changelog only shows issues fixed between releases. We are
> working on adding a custom search filter to show the list of issues
> resolved since the most recent release.
>
> There is also a link called "Resolved Recently" on the top-level issue
> tracker page:
> http://framework.zend.com/issues/secure/Dashboard.jspa
>
> Cheers,
> Gavin
>
> gonyuu wrote:
>> As an aside, where can I find out when these changes are officially
>> implemented (i.e. when they will appear in the latest snapshot/nightly
>> build)? Do I just have to follow the issue tracker?
>>
>> Thanks, gonyuu.
>>
>>
>> GavinZend wrote:
>>
>>> This is recognized as an issue:
>>> http://framework.zend.com/issues/browse/ZF-50
>>>
>>> We are going to propose introducing a name filter for database names,
>>> table names, and column names, with a default behavior. The default
>>> behavior will be "no filtering" or modification of these names (i.e. no
>>> more camelCase). Users will then be able to select whatever "name"
>>> filter they need for their particular circumstances, if the default
>>> doesn't work.
>>>
>>> Cheers,
>>> Gavin
>>>
>>> Which ZF List?
>>> =
>>> Everything, except the topics below: fw-general@lists.zend.com
>>>
>>> Authorization, Authentication, ACL, Access Control, Session Management
>>> [EMAIL PROTECTED]
>>>
>>> Tests, Caching, Configuration, Environment, Logging
>>> [EMAIL PROTECTED]
>>>
>>> All things related to databases
>>> [EMAIL PROTECTED]
>>>
>>> Documentation, Translations, Wiki Manual / Tutorials
>>> [EMAIL PROTECTED]
>>>
>>> Internationalization & Localization, Dates, Calendar, Currency, Measure
>>> [EMAIL PROTECTED]
>>>
>>> Mail, MIME, PDF, Search, data formats (JSON, ...)
>>> [EMAIL PROTECTED]
>>>
>>> MVC, Controller, Router, Views, Zend_Request*
>>> [EMAIL PROTECTED]
>>>
>>> Community Servers/Services (shell account, PEAR channel, Jabber)
>>> [EMAIL PROTECTED]
>>>
>>> Web Services & Servers (HTTP, SOAP, Feeds, XMLRPC, REST)
>>> [EMAIL PROTECTED]
>>>
>>>
>>> How to subscribe: http://framework.zend.com/wiki/x/GgE
>>>
>>> Abu Hurayrah wrote:
>>>
>>>> Since you've brought it up, is there anywhere where I can see the
>>>> explanation/justification given for this automatic routine? I think
>>>> it makes ZF a lot harder to work with when you use it with older
>>>> systems where the schema name system may be a mix of different
>>>> styles...StudlyCaps, camelCase, underscore_separated, or allinone.
>>>> Short of rewriting the __get() & __set() methods for each class/object
>>>> you want to use, is there any other easy way to handle this?
>>>>
>>>> Abu Hurayrah
>>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>>>> Hidayah Online - Guidance According to the Qur'an and Sunnah
>>>> <http://hidayahonline.org/>
>>>> `A'isha, the wife of Allah's Apostle (may peace be upon him), reported
>>>> Allah's Apostle (may peace be upon him) as saying:
>>>> /Kindness is not to be found in anything but that it adds to its
>>>> beauty and it is not withdrawn from anything but it makes it
>>>> defective./
>>>> narrated in Sahih Muslim, Book 3, Number 6274
>>>>
>>>>
>>>> gonyuu wrote:
>>>>
>>>>> I think what Bruno is referring to is the camel-case renaming of the
>>>>> fields
>>>>> in Zend_Db_Row; i.e. "zend_field" gets mapped as zendField. I ran
>>>>> into the
>>>>> same problems when I had fields named "ZendField". I basically
>>>>> couldn't
>>>>> access these fields because of the case sensitivity in MySQL
>>>>> ("zendfield"
>>>>> would
Re: [fw-general] Zend_Db_Table
As an aside, where can I find out when these changes are officially
implemented (i.e. when they will appear in the latest snapshot/nightly
build)? Do I just have to follow the issue tracker?
Thanks, gonyuu.
GavinZend wrote:
>
> This is recognized as an issue:
> http://framework.zend.com/issues/browse/ZF-50
>
> We are going to propose introducing a name filter for database names,
> table names, and column names, with a default behavior. The default
> behavior will be "no filtering" or modification of these names (i.e. no
> more camelCase). Users will then be able to select whatever "name"
> filter they need for their particular circumstances, if the default
> doesn't work.
>
> Cheers,
> Gavin
>
> Which ZF List?
> =
> Everything, except the topics below: fw-general@lists.zend.com
>
> Authorization, Authentication, ACL, Access Control, Session Management
> [EMAIL PROTECTED]
>
> Tests, Caching, Configuration, Environment, Logging
> [EMAIL PROTECTED]
>
> All things related to databases
> [EMAIL PROTECTED]
>
> Documentation, Translations, Wiki Manual / Tutorials
> [EMAIL PROTECTED]
>
> Internationalization & Localization, Dates, Calendar, Currency, Measure
> [EMAIL PROTECTED]
>
> Mail, MIME, PDF, Search, data formats (JSON, ...)
> [EMAIL PROTECTED]
>
> MVC, Controller, Router, Views, Zend_Request*
> [EMAIL PROTECTED]
>
> Community Servers/Services (shell account, PEAR channel, Jabber)
> [EMAIL PROTECTED]
>
> Web Services & Servers (HTTP, SOAP, Feeds, XMLRPC, REST)
> [EMAIL PROTECTED]
>
>
> How to subscribe: http://framework.zend.com/wiki/x/GgE
>
> Abu Hurayrah wrote:
>> Since you've brought it up, is there anywhere where I can see the
>> explanation/justification given for this automatic routine? I think
>> it makes ZF a lot harder to work with when you use it with older
>> systems where the schema name system may be a mix of different
>> styles...StudlyCaps, camelCase, underscore_separated, or allinone.
>> Short of rewriting the __get() & __set() methods for each class/object
>> you want to use, is there any other easy way to handle this?
>>
>> Abu Hurayrah
>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>> Hidayah Online - Guidance According to the Qur'an and Sunnah
>> <http://hidayahonline.org/>
>> `A'isha, the wife of Allah's Apostle (may peace be upon him), reported
>> Allah's Apostle (may peace be upon him) as saying:
>> /Kindness is not to be found in anything but that it adds to its
>> beauty and it is not withdrawn from anything but it makes it defective./
>> narrated in Sahih Muslim, Book 3, Number 6274
>>
>>
>> gonyuu wrote:
>>> I think what Bruno is referring to is the camel-case renaming of the
>>> fields
>>> in Zend_Db_Row; i.e. "zend_field" gets mapped as zendField. I ran
>>> into the
>>> same problems when I had fields named "ZendField". I basically couldn't
>>> access these fields because of the case sensitivity in MySQL
>>> ("zendfield"
>>> would not work). My solution thus far has been to bear with
>>> lower-case field
>>> names :(
>>>
>>> gonyuu
>>>
>>>
>>> Terry Cullen wrote:
>>>
>>>> The manual:
>>>>
>>>>
>>>> >>> class ClassName extends Zend_Db_Table
>>>> {
>>>> // default table name is 'class_name'
>>>> // but we want to map to something else
>>>> protected $_name = 'another_table_name';
>>>> }
>>>> ?>
>>>>
>>>>
>>>>
>>>> On 10/2/06, Bruno Viana <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> I use the Zend_Db_Table with a test table, it works fine.. but when
>>>>> i use
>>>>> table of my old app that fields are in upper case it's don't work,
>>>>> but i
>>>>> rewrite my fields to lower case it works.
>>>>>
>>>>> I had to rewrite all my fields to lower case or have a fix (or work
>>>>> around) to this?
>>>>>
>>>>> --
>>>>> "Fui para os bosques viver de livre vontade. Para sugar todo o
>>>>> tutano da
>>>>> vida, para aniquilar tudo o que não era vida e para, quando morrer,
>>>>> não
>>>>> descobrir que não vivi."
>>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Zend_Db_Table-tf2369500s16154.html#a6748917
Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Zend_Db_Table
I think what Bruno is referring to is the camel-case renaming of the fields
in Zend_Db_Row; i.e. "zend_field" gets mapped as zendField. I ran into the
same problems when I had fields named "ZendField". I basically couldn't
access these fields because of the case sensitivity in MySQL ("zendfield"
would not work). My solution thus far has been to bear with lower-case field
names :(
gonyuu
Terry Cullen wrote:
>
> The manual:
>
>
> class ClassName extends Zend_Db_Table
> {
> // default table name is 'class_name'
> // but we want to map to something else
> protected $_name = 'another_table_name';
> }
> ?>
>
>
>
> On 10/2/06, Bruno Viana <[EMAIL PROTECTED]> wrote:
>>
>> I use the Zend_Db_Table with a test table, it works fine.. but when i use
>> table of my old app that fields are in upper case it's don't work, but i
>> rewrite my fields to lower case it works.
>>
>> I had to rewrite all my fields to lower case or have a fix (or work
>> around) to this?
>>
>> --
>> "Fui para os bosques viver de livre vontade. Para sugar todo o tutano da
>> vida, para aniquilar tudo o que não era vida e para, quando morrer, não
>> descobrir que não vivi."
>
>
--
View this message in context:
http://www.nabble.com/Zend_Db_Table-tf2369500s16154.html#a6739263
Sent from the Zend Framework mailing list archive at Nabble.com.
[fw-general] Zend_Filter_Input, toArray() method
This is a small idea, but wouldn't a toArray() be pertinent for the
Zend_Filter_Input class, especially since Zend_Filter_Input destroys its
source? I very much appreciate the filtering methods available through
Zend_Filter_Input, but sometimes I find that an array() structure would be
convenient (for looping, especially).
public function toArray()
{
return $this->_source;
}
use case:
foreach($zendFilter->toArray() as $key) {
echo $zendFilter->getAlnum($key);
}
Thanks, gonyuu
--
View this message in context:
http://www.nabble.com/Zend_Filter_Input%2C-toArray%28%29-method-tf2414124s16154.html#a6729283
Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Controller noRouteAction()
Great advice. I like very much your wrapper "approach", especially the bit
about implementing authentication within the interface. That's exactly the
simplification I was looking for. Thanks!
And after giving it a bit more thought, I actually think that the current
approach is quite reasonable. Overloading __call is not much of a hassle,
and being able to distinguish between a garbage controller and a garbage
action of a legitimate controller could be convenient. The $methodName
parameter is also pretty handy at times for debugging or even notifying
admins to user activity. For example, $methodName's could be logged or
e-mailed to an admin, serving as a warning to common 404 errors (which would
be redirected) or even a caution that a snoop is looking for restricted
files (also redirected).
But anyway, thanks Simon for the tip.
Simon Mundy wrote:
>
> Hi Gonyuu
>
> Work on the new MVC is commencing so all current issues will probably
> be delayed in being resolved/examined for a short while. However the
> problem you describe isn't necessarily an 'issue', more an approach.
>
> If it helps you, my approach is to make an abstract Action controller
> for each of my projects (e.g. class Myproject_Action_Controller
> extends Zend_Controller_Action) and to then put the 'norouteAction'
> method in that. It makes more sense for me to do that as I can then
> gracefully catch errors and display them on a per-site basis to avoid
> a more 'templated' approach. It's also a good idea to create a
> wrapper such as this to envelop any application-specific logic such
> as authentication.
>
> Cheers
>
>>
>> Hello all,
>>
>> Has this issue been resolved? The solution proposed here sounds
>> perfect, and
>> the fix seems quite easy. When might it be implemented? I don't see
>> it as of
>> the latest developer release.
>>
>> Associated Issue/Bug Link: http://framework.zend.com/issues/browse/
>> ZF-310
>>
>> Thanks, gonyuu
>>
>>
>> Chad Minick wrote:
>>>
>>> Hello, I have been lurking on this mailing list for quite awhile,
>>> trying
>>> to find my niche where I feel comfortable to contribute, but I
>>> thought I
>>> at least try to develop an application with ZF before I put in my 2
>>> cents. I started to develop my blog with ZF 0.1.5.
>>>
>>> I started out with my index.php and in it I have the following
>>> controller and routers set up.
>>> //Router
>>> $router = new Zend_Controller_RewriteRouter();
>>> //add Routes here
>>> $router->addRoute('admin','admin/:action/:id',array('id' =>
>>> null,'controller' => 'admin', 'action' => 'index'));
>>> //pass it to the controller
>>> $ctrl = Zend_Controller_Front::getInstance();
>>> $ctrl->setRouter($router);
>>> $ctrl->setControllerDirectory('./private/c');
>>>
>>> I set up my IndexController, with an indexAction and a noRouteAction.
>>> I also set up an AdminController, with an indexAction, and thought
>>> that
>>> a noRouteAction would be appropriate there too.
>>>
>>> Everything is working great except when I pass a nonesense route
>>> to the
>>> admin controller, I get the exception thrown by __call() in
>>> Zend/Controller/Action.php. (blahblahAction() does not exist). It
>>> only
>>> took a few minutes to realize that I could over ride __call() in
>>> AdminController to acheive the same results as IndexController's
>>> noRouteAction. Everything works like I think it should now.
>>>
>>> So my question is two fold:
>>> 1. Am I doing something wrong?
>>> 2. If I am not doing something wrong, would it be more intuitive
>>> to give
>>> every Controller a noRouteAction that could possibly redirect to a
>>> known
>>> route or possibly throw a 404? I first added it because I thought if
>>> that's how IndexController works, that's how they all should work.
>>>
>>> Thanks in advance for any feedback.
>>>
>>> Chad Minick
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Controller-
>> noRouteAction%28%29-tf2006115.html#a6700911
>> Sent from the Zend Framework mailing list archive at Nabble.com.
>>
>
> --
>
> Simon Mundy | Director | PEPTOLAB
>
> """ " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
> 202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
> Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654
> 4124
> http://www.peptolab.com
>
>
>
>
--
View this message in context:
http://www.nabble.com/Controller-noRouteAction%28%29-tf2006115.html#a6701106
Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Controller noRouteAction()
Hello all,
Has this issue been resolved? The solution proposed here sounds perfect, and
the fix seems quite easy. When might it be implemented? I don't see it as of
the latest developer release.
Associated Issue/Bug Link: http://framework.zend.com/issues/browse/ZF-310
Thanks, gonyuu
Chad Minick wrote:
>
> Hello, I have been lurking on this mailing list for quite awhile, trying
> to find my niche where I feel comfortable to contribute, but I thought I
> at least try to develop an application with ZF before I put in my 2
> cents. I started to develop my blog with ZF 0.1.5.
>
> I started out with my index.php and in it I have the following
> controller and routers set up.
> //Router
> $router = new Zend_Controller_RewriteRouter();
> //add Routes here
> $router->addRoute('admin','admin/:action/:id',array('id' =>
> null,'controller' => 'admin', 'action' => 'index'));
> //pass it to the controller
> $ctrl = Zend_Controller_Front::getInstance();
> $ctrl->setRouter($router);
> $ctrl->setControllerDirectory('./private/c');
>
> I set up my IndexController, with an indexAction and a noRouteAction.
> I also set up an AdminController, with an indexAction, and thought that
> a noRouteAction would be appropriate there too.
>
> Everything is working great except when I pass a nonesense route to the
> admin controller, I get the exception thrown by __call() in
> Zend/Controller/Action.php. (blahblahAction() does not exist). It only
> took a few minutes to realize that I could over ride __call() in
> AdminController to acheive the same results as IndexController's
> noRouteAction. Everything works like I think it should now.
>
> So my question is two fold:
> 1. Am I doing something wrong?
> 2. If I am not doing something wrong, would it be more intuitive to give
> every Controller a noRouteAction that could possibly redirect to a known
> route or possibly throw a 404? I first added it because I thought if
> that's how IndexController works, that's how they all should work.
>
> Thanks in advance for any feedback.
>
> Chad Minick
>
>
--
View this message in context:
http://www.nabble.com/Controller-noRouteAction%28%29-tf2006115.html#a6700911
Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Keeping up with the latest developer code
Thanks Martel! That did the trick.
Do you have an idea as to why my base directory detection might have failed?
Martel Valgoerad wrote:
>
> gonyuu wrote:
>
>> I've been having some troubles myself with the latest controller.
>> Firstly,
>> it seems you must provide a RewriteRouter, else an exception will be
>> caught
>> and a "404" error will display, defaulting to the noRouteAction(). So:
>>
>> $route = new Zend_Controller_RewriteRouter();
>> $ctrl = Zend_Controller_Front::getInstance();
>> $ctrl->setRouter($route);
>> $ctrl->run('/path/to/controller');
>>
>>>From here, I assumed that RewriteRouter's included 'default' or 'compat'
>> routes would take care of the basic routing for :controller/:action, but
>> all
>> of my routes get sent to index/index for whatever URL I supply.
>>
>> Could someone help us out with this? Or point us to where there is
>> documentation on the changes that've been committed?
>
> $route = new Zend_Controller_RewriteRouter();
>
> Now provide a rewrite base which was probably incorrectly detected with
> your setup.
> Set it to a slash '/' if you run from root dir or a '/subdir' if you run
> your app
> from within a webserver subdirectory:
>
> $route->setRewriteBase('/');
>
> $ctrl = Zend_Controller_Front::getInstance();
> $ctrl->setRouter($route);
> $ctrl->run('/path/to/controller');
>
> --
> Martel Valgoerad aka Michal Minicki | [EMAIL PROTECTED] |
> http://aie.pl/martel.asc
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> "Idleness is not doing nothing. Idleness is being free to do anything." --
> Floyd Dell
>
>
--
View this message in context:
http://www.nabble.com/Keeping-up-with-the-latest-developer-code-tf2386608s16154.html#a6685122
Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Keeping up with the latest developer code
All,
I've been having some troubles myself with the latest controller. Firstly,
it seems you must provide a RewriteRouter, else an exception will be caught
and a "404" error will display, defaulting to the noRouteAction(). So:
$route = new Zend_Controller_RewriteRouter();
$ctrl = Zend_Controller_Front::getInstance();
$ctrl->setRouter($route);
$ctrl->run('/path/to/controller');
>From here, I assumed that RewriteRouter's included 'default' or 'compat'
routes would take care of the basic routing for :controller/:action, but all
of my routes get sent to index/index for whatever URL I supply.
Could someone help us out with this? Or point us to where there is
documentation on the changes that've been committed?
Thanks, gonyuu
Epong Yu wrote:
>
> To keep up with the development of the Zend Framework and to prevent a
> major
> overhaul of my application when ZF releases a stable, final build, I've
> been
> trying to keep up with the developer code via SVN. Already, however, I'm
> having major problems. Specifically, Zend_Controller_Front isn't
> redirecting
> to the proper controller/action. Did I miss something? Has there been a
> major change in the controller setup?
>
> Essentially, if I have:
>
> include_once('Zend.php');
> Zend::loadClass('Zend_Controller_Front');
> $controller = Zend_Controller_Front::getInstance();
> $controller->run('./app/controllers');
>
> I'd just like to confirm that this is still the correct way to initialize
> the Zend Controller.
>
> With other issues, is there somewhere I can go to read up on the major
> changes that have already been committed? Will there be a "upgrade
> tutorial"
> for those upgrading from 0.1.5, explaining specifically what's
> changed/improved/added/removed, instead of just having users decipher an
> updated, new manual? I find it nearly impossible to keep up with the
> changes
> in Zend using the Issue Tracker. I also have this:
> http://framework.zend.com/wiki/display/ZFPROP/Home to look forward to, but
> it seems that smaller, syntactical changes like this:
> http://www.nabble.com/API-change-in-the-RewriteRouter-tf1943012.html#a5327149,
> aren't necessarily covered there.
>
> Thanks, delsvr
>
>
--
View this message in context:
http://www.nabble.com/Keeping-up-with-the-latest-developer-code-tf2386608s16154.html#a6683082
Sent from the Zend Framework mailing list archive at Nabble.com.
