Image
EAN-139780834116511   EAN-13 barcode 9780834116511
Product NameThe 19th Century Holiness Movement: Volume 4 (Great Holiness Classics)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 0834116510
SKU9780834116511
Price New39.99 US Dollars    (curriencies)
Price Used64.99 US Dollars    (curriencies)
Width1.23 inches    (convert)
Height8.84 inches    (convert)
Length5.92 inches    (convert)
Weight22.08 ounces    (convert)
AuthorMelvin E. Dieter
Page Count416
BindingHardcover
Published07/01/1998
FeaturesUsed Book in Good Condition
Long DescriptionNot since apostolic times had a greater thrust of evangelism and missionary fervor been seen than during the 19th century. Inevitably this Holiness revival brought a greater awareness and interest in the work of the Holy Spirit. This volume is a compilation of testimonies, sermons, and other writings of well-known Holiness leaders such as William Adams, Aaron Lummus, Orange Scott, Phoebe Palmer, Whitall Smith, Benjamin T. Roberts, Martin Wells Knapp, Phineas Bresee, and many others. This is volume 4 in the six-volume set of Great Holiness Classics. Cloth.
Similar Items9781149409091: The Holiness Revival of the Nineteenth Century
9781149030080: The Holiness Revival of the Nineteenth Century
9781146796088: The Holiness Revival of the Nineteenth Century
9781146787260: The Holiness Revival of the Nineteenth Century
9781144419620: The Holiness Revival of the Nineteenth Century
9781143712012: The Holiness Revival of the Nineteenth Century
9781142141318: The Holiness Revival of the Nineteenth Century
9780810831551: The Holiness Revival Of The Nineteenth Century
9780801031588: The Politics Of Discipleship: Becoming Postmaterial Citizens (The Church And Postmodern Culture)
9780521426169: Self And Salvation: Being Transformed (Cambridge Studies In Christian Doctrine)
View 19 more similar items
Created06-14-2012 1:05:00am
Modified05-01-2020 3:54:30am
MD5f0f1b2d3ebc1f8663e5e96443e2b1583
SHA256d7a7f1f9e48679a81febfca6b44d4a2e0b99e681c37f7c8887f0547ce377aec7
Search Googleby EAN or by Title
Query Time0.0209990

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

Close

Dialog