Image
EAN-130012569797284   EAN-13 barcode 0012569797284
UPC-A012569797284   UPC-A barcode 012569797284
Product NameHot Rods to Hell
LanguageEnglish
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B000OHZJIM
Model2287094
Price New8.99 US Dollars    (curriencies)
Price Used5.77 US Dollars    (curriencies)
IMDbIMDb Link
Run Time92 minutes
CastDana Andrews, Jeanne Crain, Mimsy Farmer, Laurie Mock
DirectorJohn Brahm
GenreACTION,DRAMA,THRILLER
Run Time100 minutes
Width5.5 inches    (convert)
Height0.53 inches    (convert)
Length7.5 inches    (convert)
Weight40 hundredths pounds    (convert)
AuthorAlex Gaby
BindingDVD
Release Year1967
FormatMultiple Formats, Closed-captioned, Color, NTSC, Subtitled, Widescreen
Run Time100 minutes
FeaturesShrink-wrapped
Long DescriptionWhile on a business trip just before Christmas, Tom Phillips gets into a car accident, which was caused by the reckless driving of the other car involved. Although Tom suffered no paralysis from his back injury, he did come out of the accident with a chronic back problem which results in him not being able to continue with his current work, and a mental block having anything to do with the accident, including Christmas music, driving in general and the sounds of screeching tires and breaking glass. The Phillips - Tom, his wife Peg, and their two children, teenager Tina and pre-teen Jamie - end up moving from their Boston home and buying a motel in Mayville in the California desert. Tom would be physically able to do the work required running a motel, and the dry heat is good for his back. But as they approach Mayville, they encounter a bunch of reckless hot rodders named Duke, Ernie and Gloria. Since Tom scolds them about their reckless behavior, they decide to make the Phillips' lives miserable by terrorizing them using their souped up vehicle. They also end up finding out where the Phillips' ultimate destination is. But as their string of altercations comes to a head, the process which includes Tina's teen-aged infatuation with Duke, the Phillips have to figure out how best to protect themselves, Tom who knows they can't outrun the souped up hot rod, or out "chicken" the crazed Duke.
Similar Items0766483314767: Hot-Rod Girl
0715515137614: Two-Lane Blacktop
0683904540102: White Line Fever - 40th Anniversary Series
0089859824722: Funny Car Summer
0089218419798: Hot-Rod Girl
0025192360428: More American Graffiti
0011929310057: Hot Rods, Rat Rods & Kustom Kulture Back from the Dead - The Complete Build
0011929310002: Hot Rods, Rat Rods Back from Dead
0011301690234: California Kid
0011301604972: Aloha, Bobby and Rose
View 7 more similar items
Created05-22-2010
Modified06-05-2019 5:17:59pm
MD56e872c5a04eb99107692c25399160688
SHA2569c3bbca444b87de3b0812e966f592e7e1353325592cc1d0dfa73255ac19236d9
Search Googleby EAN or by Title
Query Time0.0276361

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share