You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Facebook uses the og:url tag to identify actions such as likes and shares aggregate at the same URL rather than spreading across multiple versions of a page.
This leads to a problems described in #104, because we're using the current URL of an item, which is calculated dynamically and inserted in the template using this:
I propose the following implementation with support only for Dexterity-based content types:
create a Social Media behavior that could be applied to any content
this behavior will add a new read-only field that will contain the canonical URL of an item
the canonical URL will be populated on an event subscriber using information stored in the configlet and the path of the item
the configlet should store the schema and domain name that is being used on a site, for instance http://www.example.org/
this will solve the following issues:
migration to HTTPS as the user just have to edit the configuration field in the configlet and change the schema to https://www.example.org/; all items previously published will keep the original canonical URL and no counters will be lost
migration to a different domain name will be handled in a similar way by just updating the configuration field in the configlet with something like https://www.example.com/
rename of items will keep also the original canonical URL
other problems that we need to solve:
what happens with content already in place? we will need to provide a script to populate content already published that has no canonical URL defined
Facebook uses the
og:url
tag to identify actions such as likes and shares aggregate at the same URL rather than spreading across multiple versions of a page.This leads to a problems described in #104, because we're using the current URL of an item, which is calculated dynamically and inserted in the template using this:
I propose the following implementation with support only for Dexterity-based content types:
http://www.example.org/
this will solve the following issues:
https://www.example.org/
; all items previously published will keep the original canonical URL and no counters will be losthttps://www.example.com/
other problems that we need to solve:
The text was updated successfully, but these errors were encountered: