Taco and tea do taste good as breakfast...yumm....now, this is going
to be a long read, so I would encourage you get some tea too
The Facebook like button integration runs on JavaScript. The
acceptable solution is to make the various meta object available in
the DOM before the Facebook JavaScript runs.
Please try Markus solution before trying mine.
The solution that do not reduce CMS performance: Use JavaScript/
JQuery to create the meta objects in the DOM
<script>
// going to create just 1 field as an example
// add current page headline
$("head").append("<meta property=\"og:title\" content=\"<%hdl_title%>
\" />";
</script>
The solution that will introduce at least +1 second to SmartEdit view,
Page preview, and publishing for all pages: Use preexecution
declare this function in the body page and foundation page
<%
Function GetPageTitle()
GetPageTitle = "<%hdl_title%>"
End Function
%>
In the <HEAD> section, have the following code
<meta property="og:title" content="<%= GetPageTitle() %>" />
On Feb 16, 6:54 pm, Markus Giesen <markus.gie...@gmail.com> wrote:
> Hi David,
>
> so essentially you'd like to decide what to put in the <head> tag
> based on the content of your page inside the target container, right?
> I'd try and read up on the transfer element.
> It can send values from inside the page within the target container to
> the parent page holding the container.
> This should be your foundation page.
> From there you should be able to test on the value of the transfer
> element whether or not it is set to addFacebookLike (or any other
> value you define) via render tags.
> There is a render tag if else query example
> here:http://www.reddotcmsblog.com/render-tags-an-overview
>
> I am not too sure if it works with transfer elements but please let us
> know how you go and drop any other questions here.
>
> Markus
>
> On Feb 17, 10:11 am, redDolt <d.alan.pr...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hello all!
>
> > I'm attempting to make sure we're not the last website on the internet
> > without a "like" button on our press release/product pages but I'm
> > running into some snags.
>
> > The current recommended implementation of facebook "like" buttons
> > includes posting some metadata tags to the page to facilitate how the
> > link appears on facebook and report on it (OpenGraph tags). For
> > example:
>
> > <meta property="og:title" content="" />
> > <meta property="og:type" content="" />
> > <meta property="og:url" content="" />
> > <meta property="og:image" content="" />
> > <meta property="og:site_name" content="" />
> > <meta property="fb:admins" content="" />
>
> > Our product pages are a "foundation" type page, so i have full access
> > to put content in the <head> of the page and populate all those tags.
>
> > However, our news articles and press releases are the "classic" leaf
> > pages, set up using target containers. This has me pretty stumped
> > about how to populate some of the tags. title and url seem easy enough
> > using info placeholders (the site map name works pretty well for title
> > and lets me specify using the data of target containers), url is the
> > url.
>
> > I could use some guidance on populating the type and image though. the
> > tags are going to either have to go into the header (shared through
> > the whole site) or into the foundation page, which is used across much
> > of the site. I dont want to hard code the type to be "article" since
> > we might conceivably want to use that foundation class for other
> > content that isnt an article and im totally clueless ways to populate
> > that image tag since the photo element will be coming from a target
> > container page. my rendertag-fu is limited but what i looked up
> > doesn't seem like I can reach into a container and then reach into an
> > element for a value.
>
> > Any advice, examples, or documentation on this would be appreciated.
>
> > David Price
> > Multiquip Inc.
--
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To post to this group, send email to reddot-cms-users@googlegroups.com.
To unsubscribe from this group, send email to
reddot-cms-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/reddot-cms-users?hl=en.
