Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Blog Comments Embed: Custom Title & Content?
boinxsoftware
Member
Hi!
We are using Vanilla Forums on our site for discussions and comments on our blog.
Now, we want to extend the Vanilla Forum Blog Comments to our FAQ section. The problem is, that the content is rendered Client-Side and defined by URLs living in the webbrowser hash (like http://domain.com/knowledge/#/product/id).
When including the Blog Comments the comment gets postet to a special category (as defined) but the discussion created there doesn't have neither content nor a valid title. The reference is set using the 'vanilla_url' parameter, otherwise it would point to http://domain.com/knowledge/ and not http://domain.com/knowledge/#/product/id.
Is there a way we can specify title and content for the forum discussion to be created? How is this content scraped from the original site? Can we so something (using user-agent based server side rendering/redirecting?) for the Vanilla Forum scraping?
Best,
Stefan from Boinx Software
We are using Vanilla Forums on our site for discussions and comments on our blog.
Now, we want to extend the Vanilla Forum Blog Comments to our FAQ section. The problem is, that the content is rendered Client-Side and defined by URLs living in the webbrowser hash (like http://domain.com/knowledge/#/product/id).
When including the Blog Comments the comment gets postet to a special category (as defined) but the discussion created there doesn't have neither content nor a valid title. The reference is set using the 'vanilla_url' parameter, otherwise it would point to http://domain.com/knowledge/ and not http://domain.com/knowledge/#/product/id.
Is there a way we can specify title and content for the forum discussion to be created? How is this content scraped from the original site? Can we so something (using user-agent based server side rendering/redirecting?) for the Vanilla Forum scraping?
Best,
Stefan from Boinx Software
This discussion has been closed.
Comments
Our page scraper takes a number of steps to try and find content. First, it looks for Facebook Open Graph tags. Then, it looks for standard meta tags on the side. Lastly, it looks at general page content.
It does this via a server-to-server cURL request, which is where the problem emerges. Because your content is generated with Javascript, the cURL request returns a page with no content. Unfortunately, there's no way to make cURL work with hashbang'd content as far as I know. You'd need to point vanilla_url to a server-generated content page.
thanks for your technical insight! After reading your response I think linking to "solid" urls (which is possible because the webapp supports HTMl5 History manipulation features) is an acceptable option. We now have some php-code on top of the application's index.html that checks whether the incoming visitor wants to see a specific article, fetches it from our API and generates the title and meta-tags before the page is delivered.
The created discussions now have the correct title and content, thank you!