Post on (not edit) a different page on your tumblr - tumblr

How do I make posts on a new page on my tumblr? For instance, my home page is just omyn.tumblr.com, where all my normal reblogs go. But I also have a page there with the URL: omyn.tumblr.com/journey
How do I make a post that posts to that page only? I don't really care if it goes on my home page at the same time it goes on my "/journey" page, so long as it at least shows up there.

There are a few ways to achieve this, both rely on Tumblr Pages.
One Post Only - Standard Layout
To show only one post, pick standard layout:
Add a page (via the customize screen), and pick standard layout.
Set the url to journey.
Add content to the page body.
The standard layout, use the Text Post Type, and the page body will render as if it was a Text Post.
Multiple Posts - Redirect
To show multiple posts, pick redirect:
Any post you want to show on your journey page, tag with journey.
omyn.tumblr.com/tagged/journey will display posts tagged journey.
Add a page (via the customize screen), and pick redirect.
Set the url to journey and redirect to omyn.tumblr.com/tagged/journey.
omyn.tumblr.com/journey will now show posts tagged journey.
These posts will still show up on the Index Page. It is possible to hide them using CSS or Javascript.

Related

Multiple share buttons that produce different content, within the same page, using Facebook OpenGraph Meta tags

I have a "single page" website. Let's call it "mySite.com/index.html".
There are several different places on my page that I would like users to share via Facebook. Each of these items should display a different image and headline text, when shared on the user's Facebook timeline.
Each of these item posts should link Facebook users back to my website, "mySite.com/index.html", when the posts are viewed from a Facebook timeline.
Example:
On my page, I wish to have two different share buttons:
A. ButtonA: This button would create a picture of an elephant on the user's Facebook timeline, with the headline, "A Beautiful Elephant!". This post on the user's timeline should link back to my page, when the post is clicked.
A. ButtonB: This button would create a picture of a tiger on the user's Facebook timeline, with the headline, "A Scary Tiger!". This post on the user's timeline should link back to my page, when the post is clicked.
The Problem:
My understanding is that in order to create Facebook timeline posts which contain attractive headline text and images, I must use Facebook OpenGraph Meta tags, on the same page that is being linked to. It seems impossible to have two different sets of Facebook meta tags on "mySite.com/index.html", one outlining the 'elephant' post, and the other outlining the 'tiger' post.
The only possible solution I can think of is this:
Create a special 'Facebook Meta HTML Page' for each post I want to make. Each 'special page would only contain the meta tags for the post I wish to outline. "mySite.com/elephant_meta.html"
The body of the special page would be blank. This will work, but there is a problem: The resulting Facebook post will link users to "mySite.com/elephant_meta.html", which is just a blank page. I wish them to be directed to "mySite.com/index.html".
Solution: Create a JavaScript redirect in the body of "mySite.com/elephant_meta.html". This redirect will take users to "mySite.com/index.html".
This will work, but it feels incredibly hacky. Is there a better way?
Still finding my way on the open graph stuff as well, but the way I understand it, you can set og:url to the url that you want users to go to when they click on the link in your story on facebook. So each of your meta pages could point back to your main site page using the og:url meta tag.

Social meta tags when several articles on same page

This is my first attempt with social share buttons on a classic HTML website (not a CMS).
I understand that social meta tags are now the way to go as you have more control on what you are sharing (you can have more control on the title, the picture, the description, the content type etc..).
What I don't get is how to share a specific article only when you have ten articles displayed on the same page.
All the tutorials I read about sharing buttons are dedicated to a whole web page but I would like to share a specific section of the page per button, not the whole page (one page = 10 articles = 10 share buttons).
How would I achieve that?
Thank you.
(Bonus question: are social meta tags shared by FB, twitter and linkedin or are they only dedicated to FB?)
I don't know if you are still struggling with this, but I've just been thinking about a similar-but-different problem, with a one-page site where the content is swapped out dynamically so that it is not possible to change the og: tags in the header.
The solution requires generating individual pages for each specific article that have their own with dedicated og: tags. Then in your page which lists 10 articles, each one has a share button where the link points to the specific article page, e.g. <a href="https://www.facebook.com/sharer/sharer.php?u=http://yoursite.com/article1.html">.
When some clicks the share button, facebook will crawl the target url for og: tags, not the page you are currently on.
In your case the solution is pretty straightforward, as you presumably have individual pages for the articles already. Mine is slightly trickier because I have to generate extra pages which won't be navigated to from my site but exist for facebook to crawl (and to display the right content when people arrive via the social shares).

2 Like buttons- one for the site, one for the post- how to?

This is for a wordpress site, but it could be for any. I want a like button at the top of the page to 'like' the whole site. I also want a like button at the end of a post to like that post.
Ok, I get that I can create two iframe buttons, using just the site url and the post url. What i dont get is how to set up the meta tags. eg, the image field would be different (site logo vs. post image)
Furthermore, I can imagine that it would be usefull to have even more like buttons, eg on a page that listed several posts, a like button on each. I realize that too many iframes will slow or stop the browser.
Mostly i just need 2 buttons, with 2 sets of info.
Yes you can add two like buttons.
for site url button set up meta tags in your home page.
for post url set up meta tags in your post page.

Adding the "Like Button" to my Facebook Page

I've found the code but not where to put it on my Facebook page.. not my website. Everyone keeps referencing dropping it in a code block, but I haven't been able to find an example of how to do this.
There's already a Like button on Facebook Pages if the user viewing the page doesn't already like the page. If you want to add a like button on your Page for another entity (such as a website, article, or a different Page) you'll need to install a tab to your page where you can put HTML content.
There are several third party applications that allow you to do this, one of the popular ones is http://www.facebook.com/apps/application.php?id=190322544333196 - you could add a new tab to your page with some static content (images, etc) and include the Like button on that tab.
There is no way to embed a like button for an external entity into a post on the page's wall, which i suspect is what you're currently trying to do.

Configuring tab with specific URL within Facebook Fan Page using app_data

The Facebook API docs say the parameter, "app_data," should be used to customize tabs within a Facebook Fan Page.
However, when users add our tab to their page, the "app_data" param gets lost every time, meaning the tabs aren't customized per Fan Page as they should be.
For instance, we want this page to get rendered for one client: http://www.facebook.com/apps/application.php?id=198939416792674&sk=app_198939416792674&app_data=15
After the client adds this URL as a tab to his Fan Page, though, the tab URL loses the "app_data" parameter. The page rendered no longer reflects the data specific to this client.
We need the tabs to contain a parameter specific to each Fan Page. We thought "app_data" was the right approach.
Any clues what we're doing wrong?
The best way to do what you trying to achieve is to customise the content based on the page['id'] that is passed to you via a signed request.