| Image |  |
| EAN-13 | 0786936709407  |
| UPC-A | 786936709407  |
| Product Name | Stay Alive - Original Theatrical Version (Full Screen Edition) |
| Language | English |
| Category | Electronics / Photography: A/V Media: Movie / TV |
| Amazon.com |  Buy on Amazon ~ B000FSL93Y |
| Price New | 24.98 US Dollars (curriencies) |
| Price Used | 1.99 US Dollars (curriencies) |
| Rating | PG-13 - Parents Strongly Cautioned |
| IMDb | 
|
| Run Time | 85 minutes |
| Aspect Ratio | 1.33:1 |
| Cast | Frankie Muniz, Jimmi Simpson, Jon Foster, Samaire Armstrong, Wendell Pierce |
| Run Time | 85 minutes |
| Width | 5.5 inches (convert) |
| Height | 0.5 inches (convert) |
| Length | 7.75 inches (convert) |
| Weight | 25 hundredths pounds (convert) |
| Binding | Dvd |
| Format | Color, Dolby, Full Screen, NTSC |
| Run Time | 85 minutes |
| Features | IN THEATERS MARCH 24, 2006 This pop culture-laden fright-fest takes the legend of Countess Elizabeth Bathory of Hungary and relocates it in the inherently creepy locale of New Orleans. The usual cast of motley and none-too-bright teenagers is assembled and attached to quirky names--smartass Phineas (Jimmi Simpson) and his Goth-girl sister, October (Sophia Bush), hunky protagonist Hutch (Jon Foster |
| Long Description | Get ready for supernatural chills and terrifying challenges in STAY ALIVE, the mind-bending thriller about a killer video game. The real world and the game world gruesomely collide when a group of friends play STAY ALIVE, a mysterious underground videogame that kills the gamer whose character dies in play. Inspired by the shocking true story of the 17th century serial killer known as the Blood Countess, the videogame gives disturbing new meaning to the phrase "game over." In a death defying race against time, the survivors must solve the mystery of the game while desperately trying to stay alive. |
| Similar Items | 0014381686722: Idle Hands 0014381685220: Darkness Falls (2003/ Image/ Special Edition) 0085391119067: Thirteen Ghosts 0883476028958: Pulse 3 Pack 0085391119036: Ghost Ship 0024543631491: Jennifer's Body 0025192032387: Last House on the Left 0883929067701: House on Haunted Hill / Return to House on Haunted Hill 0013132139593: Crazies (2010) 0025192884924: Dead Silence Dvd |
| Created | 05-22-2010 |
| Modified | 09-06-2018 1:26:47am |
| MD5 | a08936fadeceff1a54f52abef326332a |
| SHA256 | 419cb0dbeb346d0e62562f30665887f13cadcd144f4bca72707c4f3aaa8a9e9a |
| Search Google | by EAN or by Title |
| Query Time | 0.0193820 |
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.
- Unknown (should never actually appear in the API)
- Yes (a production image exists)
- No (there is no image)
- Pending (a pending image exists)
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.
- If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
- 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.