Why do you think this is wrong in 2.0?

-- 
Larry E. Masters


On Wed, Dec 22, 2010 at 2:11 PM, Ryan Schmidt <[email protected]>wrote:

> As I'm refining the bake templates for my own needs, I thought it would be
> prudent to adopt some changes from CakePHP 2.0 to give myself a head start.
> In perusing the 2.0 template files, I think I've discovered an error.
>
> In CakePHP 1.3.6, the file cake/console/templates/default/views/form.ctp
> contains this line:
>
>                <legend><?php printf("<?php __('%s %s'); ?>",
> Inflector::humanize($action), $singularHumanName); ?></legend>
>
> But in 2.0, it has been changed to read:
>
>                <legend><?php printf("<?php __('%s %s', true); ?>",
> Inflector::humanize($action), $singularHumanName); ?></legend>
>
> Given what I understand about the (much-welcomed) changes to the __()
> function in 2.0, I believe in 2.0 the line should in fact read:
>
>                <legend><?php printf("<?php echo __('%s %s'); ?>",
> Inflector::humanize($action), $singularHumanName); ?></legend>
>
> Can someone confirm or deny this? If confirmed, what is the correct way to
> report this problem to the developers?
>
>
>
> Check out the new CakePHP Questions site http://cakeqs.org and help others
> with their CakePHP related questions.
>
> You received this message because you are subscribed to the Google Groups
> "CakePHP" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<cake-php%[email protected]>For
>  more options, visit this group at
> http://groups.google.com/group/cake-php?hl=en
>

Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en

Reply via email to