| # |
Aug 14th 2009, 15:55 |
alkemann |
because of /pages/home and / |
| # |
Aug 14th 2009, 15:55 |
alkemann |
i got this on my website's public layout : <link rel="canonical" href="http://illustrata.no<?php echo $html->url(); ?>"> |
| # |
Aug 14th 2009, 15:54 |
alkemann |
if for no other reason than stop critics that read an article about duplciate content ;) |
| # |
Aug 14th 2009, 15:53 |
poLK |
markstory: yes, it produces (1.2) <link href="http://example.com" rel="canonical" /> |
| # |
Aug 14th 2009, 15:53 |
alkemann |
since cakephp routes creates "problems" of duplicate content, I think it could be worth while to have a more direct support for it |
| # |
Aug 14th 2009, 15:52 |
markstory |
easiest enhancement ever. |
| # |
Aug 14th 2009, 15:52 |
markstory |
poLK: if that works my job is done then :) |
| # |
Aug 14th 2009, 15:52 |
alkemann |
markstory: google supports it. what else matters ;) |
| # |
Aug 14th 2009, 15:52 |
poLK |
(uses 'metalink' tag) |
| # |
Aug 14th 2009, 15:52 |
alkemann |
+t |
| # |
Aug 14th 2009, 15:52 |
poLK |
does exactly the same thing |
| # |
Aug 14th 2009, 15:52 |
alkemann |
poLK: yes. that was my though |
| # |
Aug 14th 2009, 15:52 |
poLK |
$html->meta(array('link' => 'http://example.com', 'rel' => 'canonical')) |
| # |
Aug 14th 2009, 15:51 |
ADmad |
he has given referencs for google and bing |
| # |
Aug 14th 2009, 15:51 |
markstory |
I thought I remembered support being spotty. |
| # |
Aug 14th 2009, 15:50 |
markstory |
is canonical even being supported? |
| # |
Aug 14th 2009, 15:50 |
markstory |
where is the patch? |
| # |
Aug 14th 2009, 15:49 |
ADmad |
this is what he says at the end "Hopefully the CakePHP development team will include canonical support in the next version of HtmlHelper under the $html->meta() method" |
| # |
Aug 14th 2009, 15:47 |
poLK |
alkemann: I think it is work for existing HtmlHelper::$tags 'metalink' => '<link href="%s"%s/>' |
| # |
Aug 14th 2009, 15:46 |
ADmad |
guess can do that since his article content is what matters more then the 2 line helper |
| # |
Aug 14th 2009, 15:42 |
alkemann |
http://bakery.cakephp.org/articles/view/canonical-helper-reducing-duplicate-content-issues - i like the content, but not the solution. to bad we done have bakery 2.0 with the markers yet. maybe make it a tutorial instead of code/helper ? |
| # |
Aug 14th 2009, 15:04 |
poLK |
alkemann: yes, similar one. |
| # |
Aug 14th 2009, 15:03 |
alkemann |
poLK: sounds like my Multilingual behaviour |
| # |
Aug 14th 2009, 15:00 |
poLK |
sky_l3ppard: now, this article needs just some spell/grammary check |
| # |
Aug 14th 2009, 14:58 |
sky_l3ppard |
i'm away for 15 min |
| # |
Aug 14th 2009, 14:58 |
poLK |
alkemann: with this behavior, one can keep default translations in original table, and let i18n table manage only non-default ones |
| # |
Aug 14th 2009, 14:57 |
poLK |
sky_l3ppard: again, 'source record' instead of db table |
| # |
Aug 14th 2009, 14:57 |
poLK |
In this case we tell Translate behavior to translate Post.title field and SmoothTranslate to create default translation records for all our app languages and do not modify title field in the source record then saved in different locale. |
| # |
Aug 14th 2009, 14:56 |
poLK |
sky_l3ppard: section 'Using the behavior': |
| # |
Aug 14th 2009, 14:56 |
sky_l3ppard |
in extensible case i unset those fields before saving if record is being modified |
| # |
Aug 14th 2009, 14:56 |
poLK |
'when', yes |
| # |
Aug 14th 2009, 14:55 |
sky_l3ppard |
core behavior also updates original record then adding new translation to the i18n table, as far as i understood |
| # |
Aug 14th 2009, 14:54 |
poLK |
ok |
| # |
Aug 14th 2009, 14:54 |
sky_l3ppard |
look it one more time please |
| # |
Aug 14th 2009, 14:54 |
poLK |
sky_l3ppard: one of reasons for your behavior is: keep default translation for 'title' in field posts.title - and core's behavior requires to remove posts.title field from db schema |
| # |
Aug 14th 2009, 14:54 |
sky_l3ppard |
) poLK now i've changed |
| # |
Aug 14th 2009, 14:53 |
alkemann |
ACTION didnt understand neither |
| # |
Aug 14th 2009, 14:53 |
poLK |
'source record translatable field untouched' speaks about record, but readers should notice that core's behavior needs to _remove_ fields from schema |
| # |
Aug 14th 2009, 14:52 |
poLK |
sky_l3ppard: my point is that your words 'source record translatable field untouched' sounds better like 'structure of original database table, used by some translated model' |
| # |
Aug 14th 2009, 14:49 |
sky_l3ppard |
the third notice, cant find there to fit it :) |
| # |
Aug 14th 2009, 14:47 |
poLK |
because it was touched by many hands from core team |