#6170: Asset.timestamp set to force not affecting image link
---------------------------+------------------------------------------------
    Reporter:  verbal      |          Type:  Bug    
      Status:  new         |      Priority:  Low    
   Milestone:  1.2.x.x     |     Component:  Helpers
     Version:  1.2 Final   |      Severity:  Normal 
    Keywords:              |   Php_version:  PHP 5  
Cake_version:  1.2.1.8004  |  
---------------------------+------------------------------------------------
 Hello,

 I'm not sure if it's a bug or by design but I have found inconsistency in
 html helper.[[BR]]
 Looking at $javascript->link() and $html->css() you check if there is
 configuration option 'Asset.timestamp' set to true or to 'force' but not
 in $html->image().[[BR]]
 For first two it's the same line:

 {{{

 ((Configure::read('Asset.timestamp') === true && Configure::read() > 0) ||
 Configure::read('Asset.timestamp') === 'force')

 }}}

 but for latter it's:

 {{{

 (Configure::read('Asset.timestamp') == true && Configure::read() > 0)

 }}}

 So when I set 'Asset.timestamp' to 'force' there are no timestamps in
 image links.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/6170>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to 
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to