Multiple same og:title alright? - facebook-like

We have a wedding photography site that I am adding the Facebook Like button to the individual image pages. Regarding Facebook and the og:title tag, is there a downside if the og:title tag is the same for each image in the gallery? Example: "John and Jane's Wedding" Or should it be "John and Jane's Wedding - image1.jpg"? I just want to make sure that if someone likes multiple images from the one gallery, that Facebook will treat each like correctly if the same title is used for each one, or do they each need to be unique? Image file names are not always pretty, such as img000014.jpg, so I would like to avoid using them if it is ok.

It may be confusing to users that different content (images in your case) have same title, but from technical perspective there is nothing wrong with it.
As long as those images have different URL's they be treated as different objects to Facebook OpenGraph (since objects are identified by URL's not titles).

Related

How to get specific episode from iTunes API?

How do I get a link to a specific episode of a TV show in the iTunes store? I have the name of the show*, the season, and episode number. From the documentation, I've found that I can get a list of episodes, and then parse the JSON to find the episode and its iTunes links.
However, the documentation also says that one should avoid making too many or too big requests (e.g. by using the limit parameter), so I'm wondering if there is a better way to directly get the desired episode link, without fetching and parsing a potentially huge list of episodes.
*) In case the season name is ambiguous, I have the TVDB data, and can also specify a 'canonical' name if neccessary.
The Search API has a few parameters that will help qualify the content you want returned.
It sounds like you should be using the Show title as the "term".
https://itunes.apple.com/search?term=Jersey+Shore&attribute=tvSeasonTerm&entity=tvEpisode
Adding "attribute=tvSeason" will ensure the term is matched only to TV Show titles and not any other meta data in the iTunes store (including music, movies, apps etc.).
Also, appending "entity=tvEpisode" will indicate to the API that you want only Episodes returned and not just the Season info (by default).

Review Site > Need common post template or plugin for product thumbnail, details and description

I'm working on a site in which each post will be dedicated to a single product review. I'd like to have a consistent look for each review so that the product image or cover art is at the top left. To the right of the product image, I'd like a listing of items (author, sales page, product cost, etc).
Below these two, I'd like a summary description area, spanning both columns. I don't want to use tables if possible (the summary description will have a clear:both setting perhaps).
Finally, I'd like to specify a list of "Related Products" in the right sidebar area. I'd like to be able to simply flag a category that contains the "related products" and have the top products in the category shown (as thumbnail images) as well as links to the product page.
Should I create a post template for this or do you have recommendations for a plugin that will work better and database each product separately (rather than placing it all in the post markup)?
TIA :)
For these specific requirements on the stuff you want displayed - yes, you need a post template. WordPress 3.0 introduces custom post types which might ease you in the work, but all the data you insert should be displayed appropriately => product post template OR a lot of html in you post, formatting all that stuff. The least doesn't have any flexibility and if hardly a solution to the problem.

Is it ok to hardcode dynamic links in a permanent view?

Let's say I wanted to showcase 2-3 clickable buttons on my homepage which will be there permanently. These are links to the css, html, and javascript tag listing pages.
Is it fine to just hardcode href=/tags/css and href=/tags/html right in my django templates/view?
I won't change them for at least a year or so, meaning I don't think I need to add a column to the tags table to distinguish them - is this common or should I try to make it somewhat dynamic? These tags are in a table but so are 1000 other tags.
Just remember to document that you did it in some place obvious, like in tagging/views.py, or maybe you have an equivalent of my When_Peter_Gets_Hit_By_A_Bus.txt, in which I document all of these types of optimizations. No, I really do have a file like that for each of my customers.

How do you post content to a specific template position?

I purchased a template / theme from RocketTheme, but I can't figure out how to add content at a specific position.
The templates have "module positions" that collapse. I'd like to add some content at one of the module positions.
If I add articles, they seem to go into "mainbody". But I'd like to have content in other areas of the template.
How do I take some text, images, or other content, and get them to display in these other positions (i.e., TOP-A, or FEATURE-A, etc)?
I've tried this
Go to Extensions->Module Manager
Select "New", Select "Sections"
Under "Details", I select Position->Top-A
I give it a title.
Nothing seems to happen. I don't see anything new exposed in the admin UI, and I don't see a way to get any content into this newly defined section. What am I not understanding?
go to JED and look up html in module or content in module or content in component there are a bunch of them. http://extensions.joomla.org/search?q=module+content&start=20
Essentially
you create and save an article. Make sure it is saved to a section or category on your menu
open the module one of the paramaters will ask for the article id...decide which position and which pages you want it on and then publish.
You can also get modules that will take some or all of your articles in a category and then show them either as a slidedhow or one randomly when someone visits the page

Limit category transclusion when using dynamically-generated categories in MediaWiki

At first I wasn't sure if a question on how to do something advanced in MediaWiki belonged here, but upon reading the faq and thinking about it, I decided that wiki markup is as much its own language as HTML and CSS, and if those questions are welcome here, then hopefully this is too! If I am wrong feel free to flag this question. Update: Well as evidenced by the 3 views this question got, I suppose that while perhaps it's within the rules of Stackoverflow, there might not be much expertise on the subject! I suppose I will need to take this question to the official forums (shudder)
The problem
On a wiki I am setting up powered my MediaWiki, I have a Template that outputs among other things dynamically created categories. This means that the page that invokes the template will be categorized based on some of the variables passed to the template. The dynamically generated categories are inside <includeonly> blocks to prevent the template page itself from getting the categories.
The problem is that I then transclude that page on to other pages, which causes the categories to be transcluded as well, and now that third page has all of the categories of all of the pages it transcluded.
I want to somehow format the template such that the page that invokes the template will make use of the categories but any pages that transclude the invoking page will not inherit the categories.
Example
Here's my best shot at an example of the setup. If this is inadequate I can provide links to my real-world example.
Template:Food
A page that takes a couple variables and outputs a highly formatted block that explains the food, including outputting a category based on the "type" variable.
Banana
This page invokes the Template:Food template with a few variables, including type set to "fruit". The result is when the user views the "Banana" page they get a nicely formatted page with some basic information about the fruit. Furthermore, if the user goes to the Category:Fruit page, they will see the Banana page listed.
Banana Nut Bread Recipe
This is the problem page. On this recipe page, the author wants to transclude all of the pages for ingredients so that each ingredient is listed in its nicely formatted block. However, when he transcludes the Banana page using {{:Banana}}, the Fruit category is transcluded along with it and now the Banana Nut Bread Recipe page is listed as being in the Fruit category which is wrong.
If I understand correctly, you want to limit the includeonly info (the category) to only depth 1 transclusion. I don't think it's possible.
Possible solutions:
1- Don't put category info into the Template:Food. Just put it directly in each ingredient page or if you really must, create a Template:Food_category or similar. Then each page could have any number of {{Food}}s and the {{food category}}s would need to be explicitly put.
The Labeled Section Transclusion extension lets you tag parts of a source article with labels, and transclude based on those tags. The tags can overlap, so that you have very granular control over what gets pulled through.
https://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion
I would think that with Labeled Section Transclusion, you could transclude both the Type:fruit and the Banana description in separate transclusion statements on the Banana page, but only pull the description through to the Recipe page.