This is based on the 8.x-2.x branch ... which isn't available in the drop down for issue creation.

Example of the problem

Configuration variables need to be changed from "amazon.configuration" to "amazon.settings".

The field formatter was causing a white screen of death until this is fixed.

Patch to follow.

CommentFileSizeAuthor
#2 2787145-02.patch797 bytesjoshmiller
Screen Shot 2016-08-19 at 3.36.17 PM.png96.76 KBjoshmiller

Comments

joshmiller created an issue. See original summary.

joshmiller’s picture

joshmiller
he/him
Primary language English
Location Indianapolis, Indiana, USA
commented
Status: Active » Needs review
StatusFileSize
new 2787145-02.patch797 bytes

Again, this is against the 8.x-2.x branch.

hideaway’s picture

hideaway commented

Actually I would like to also know what is intended way of using this module, because I just run into exactly the same problem. Why module has settings form and then it is trying to get variables from configuration? Is it settings form which should be turned to configuration? For me so far this patch looks perfectly valid, otherwise Amazon field is completely unusable.

  • marcelovani committed b53ea1f on 8.x-2.x authored by joshmiller 
    Issue #2787145 by joshmiller, hideaway: Configuration misnamed, causing...
marcelovani’s picture

marcelovani
Primary language Portuguese, Brazil
Location London
commented
Status: Needs review » Fixed

Yeah, that makes sense

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.