Maybe I'm missing something, but I was wanting to set some PDO options
(namely disabling lowercase field names in resultsets), and I could not find
any way to do this without modifying Zend/Db/Adapter/Pdo/Abstract.php (line:
104). I'm creating my $db object as such:
$db = Zend_Db::factory($dbconf
On 1/15/07, Matthew Weier O'Phinney <[EMAIL PROTECTED]> wrote:
-- Philip G <[EMAIL PROTECTED]> wrote
(on Monday, 15 January 2007, 07:02 PM -0600):
> On 1/15/07, Kelsey Sigurdur <[EMAIL PROTECTED]> wrote:
> > Within a controller you can use
> >
> > $this-> getRequest()-> getControllerName();
> >
>
-- Philip G <[EMAIL PROTECTED]> wrote
(on Monday, 15 January 2007, 07:02 PM -0600):
> On 1/15/07, Kelsey Sigurdur <[EMAIL PROTECTED]> wrote:
> > Within a controller you can use
> >
> > $this-> getRequest()-> getControllerName();
> >
> > and
> >
> > $this-> getRequest()-> getActionName();
> >
>
> T
On 1/15/07, Kelsey Sigurdur <[EMAIL PROTECTED]> wrote:
Within a controller you can use
$this->getRequest()->getControllerName();
and
$this->getRequest()->getActionName();
Tried that, it's empty:
Fatal error: Call to a member function getControllerName() on a
non-object in
/media/EXTERNAL/w
Within a controller you can use
$this->getRequest()->getControllerName();
and
$this->getRequest()->getActionName();
--
Kelsey Sigurdur
Philip G wrote:
Okay, appears to be big changes in 0.6.0. Now my site won't function
cause I can't seem to get the controller name at the controller action
l
On 1/15/07, Ken Stanley <[EMAIL PROTECTED]> wrote:
Try using $this->_getParam('controller') to access the controller, and for
the action use $this->_getParam('action').
Tried that, those return empty, too.
--
Philip
[EMAIL PROTECTED]
http://www.gpcentre.net/
Okay, appears to be big changes in 0.6.0. Now my site won't function
cause I can't seem to get the controller name at the controller action
level anymore.
I have a class with two methods that were used to return the
controller and action names. Here's the original code:
class GP_Controller_Actio
This was just a quick and dirty example for low-level usage of an email
address validator upon a single datum $someEmail. Use cases will vary.
I'm not sure I understand your question, but there is more information here:
http://framework.zend.com/wiki/x/Wi8
Best regards,
Darby
Yann Nave wrote:
>
It's look like lots of code line fore only one field.
We must charge many class to valid many field , no ?
On 1/15/07, Darby Felton <[EMAIL PROTECTED]> wrote:
Sure thing; at a low level, it might be used as follows:
require_once 'Zend/Validate/EmailAddress.php';
$validator = new Zend_Validate
Sure thing; at a low level, it might be used as follows:
require_once 'Zend/Validate/EmailAddress.php';
$validator = new Zend_Validate_EmailAddress($someOption, $anotherOption);
if ($validator->isValid($someEmail)) {
// valid...
} else {
// invalid...
foreach ($validator->getMessages()
> First, any validator is its own class under the new design,
> rather than being a single method of a larger scope,
> general-purpose validation class (as in the implementation
> currently in the framework core trunk).
Darby - do you have any information about how this new encapsulation works
Hi Andrew,
Good question - I'm not sure whether a stop-gap implementation will be
acceptable, but let me describe the current state of affairs.
First, any validator is its own class under the new design, rather than
being a single method of a larger scope, general-purpose validation
class (as in
Thought this would be an interesting read for the people here, since
the Framework is licensed under the BSD license. Note, it is based
under views on the Australian laws, and is by no means official
legal advice or a statement of the law.
http://www.groklaw.net/article.php?story=20070114093427179
I don't know Zend's position on this subject but I think a "stop-gap" version
would be a good idea. By doing this one could start using isEmail function,
instead of using a home made function, and would benefit from further updates
transparently.
Olivier
Le lundi 15 janvier 2007 13:17, Simon R
I've been looking into this and have developed what could be called a
"stop-gap" version which validates against the recommended dot-atom
character set for email addresses.
http://framework.zend.com/issues/browse/ZF-42
After Gavin's comments I'm looking into Perl's Email::Valid which also
optional
15 matches
Mail list logo
