Support » Plugin: Amazon Associates Link Builder » Links and images doesn’t show at backend

  • taisa1984

    (@taisa1984)


    Since some weeks, all my links and images, carrousels and all created with the plugin disappeared.

    I am not sure if it was caused by the WordPress updates. I tried too to rollback, and it stayed the same.

    Or maybe it is a problem with the plugin itself, with the API keys, or I don’t know. I can’t search for products, and also, the shortcodes I already had do nothing. No link, image or carrousel shows up at the website front end.

    I already tried also creating new API keys several times, and testing combinations from default marketplace, the marketplace where I got the API keys, and so. Of course I checked several times there was no extra spaces.

    I though it could be a geo-ip issue, but tried to delete de plugin and setupt it only with one amazon market, and it was the same.

    Could someone help me to get some light with this problem? I am also waiting for support reply.

    Also… I think there should be a way for the plugin to keep working (at least in some way) besides the API keys fail. At least, it could generate easily a basic link to the product without accessing the API. It only has to concat the url with the id and ASIN. That would avoid this happening (this is the second time this happens to me… and it really annoys me because I can be losing some sales at this moment with the links not showing).

    Thanks in advance.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 16 through 30 (of 41 total)
  • Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    Dear @taisa1984,

    Sincere apologies for the delayed response.

    Please make sure that you have entered your Access Key ID and Secret Access Key correctly and without any additional spaces.

    In case you are calling the Product Advertising-API (PA-API) for a marketplace different from the one you have registered for PA-API, do the following:

    Check that you are registered as an associate / affiliate in the locale for which you are making the request. On this page you can see a list of the different locales of the Amazon Associates Program. You have to be signed up to each one you want to access through PA-API, and your application has to be approved. If it has not been approved yet, you can ask for a PA-API exception following the indications on the local Associates Central page.
    Also make sure you have signed up for PA-API usage with every account by logging into the local Associates Central page and visiting its dedicated PA-API page. If the Join button appears greyed out, please check if you are signed in as the account’s primary user and if the application for your associate account has already been approved.
    If you have created accounts with separate email addresses, add the email address used for creating the PA-API account as a primary email to your existing Amazon Associates account from which you are trying to call PA-API. i.e. if you have generated PA-API credentials from a US Affiliate account with the primary email address as test@test.com, and you want to access PA-API from DE account, add test@test.com as the primary email address for DE affiliate account. For more help on changing the primary owners, please refer to this link.
    If on the on the PA-API page of the relevant marketplace’s Associates Central there is a “Migrate” button showing, we recommend to use it to migrate your PA-API access from AWS to Associates Central. This will generate a new pair of credential that you should then use for your PA-API access. In case the “Migrate” button appears greyed out, please check if you are signed in as the account’s primary user and if the application for your associate account has already been approved.

    In the case the above doesn’t help or you are using PA-API from the same primary email address, do the following:

    Using your access key & secret key credentials, please check if you can get results from ItemSearchAPI on Product Advertising API scratch pad. (Don’t forget to set the marketplace at the top to the one you are registered as an associate.).
    If the above gives an error message, follow the troubleshooting procedure link in the error message shown on PAAPI scratch-pad and share the results with us.
    If the above doesn’t solve your issue, please create a new thread with the title starting with [PA-API Credentials Issue].

    I am registered for multiple affiliate programmes in the UK, US, IT, DE etc. However, the plugin only allows a single key to be used. So in this situation how do I get the link builder to link to multiple affiliate accounts where they use different access keys?

    You can use the same PA-API keys across US, CA, MX, BR, ES, FR, IT, DE, IN & UK, if you have signed up to these locales and your application has been approved. In case one of your Amazon Associates accounts is under a different email address from the one which you have registered for PA-API, do the following:

    “If you already have an active Amazon Associates account, please add the email address used for creating the PA API account as a primary email to your existing Amazon Associates account. Once the email address is added successfully, you will be able to continue accessing the PA API. For more help on changing the primary owners, please refer to this link for detailed instructions.”

    php 7.3.0
    wordpress 5.0.3
    plugins:
    All-in-One WP Migration
    Amazon Associates Link Builde
    Autoptimize
    Cache Enabler
    Classic Editor
    Contact Form 7
    Cookie Notice
    Developer Tools
    GA Google Analytics
    Google Adsense Ads Manager
    Insert Headers and Footers
    Really Simple SSL
    Smush
    Ultimate Nofollow
    WP Fastest Cache
    WP Gallery Custom Links
    Yoast SEO
    mmm en otro dominio intento entrar con mis credenciales pero el plugin no me deja guardar. has intentado eso?

    no tiene que ver con nosotros, eso seguro. Tampoco el alojamiento ya que antes funcionaba y ahora no.

    me acabo de dar cuenta de este mensaje en otro dominio.

    La etiqueta de asociado abdallah02-20 no está presente en la lista de etiquetas válidas. La etiqueta de asociado se ha actualizado a no especificado. Verifique su selección de etiqueta de Asociado o póngase en contacto con el administrador para agregar una nueva etiqueta.

    I think everything you told me was not the problem.

    – Of course I checked lots of times the information is correct. Even made a EXACT Clone of my site, where it worked. I tried the exact same configuration in 3 other domains, where it worked. It only don’t work under my domain as I said before (I have another website in a subdomain, where it fails too).

    – I tried both configuring Spanish marketplace and german, creating the API again from the same marketplace, and configuring the plugin for that marketplace too.

    – The APIS work with other domains and also on the scratchpad.

    – The APIS are created and appear as Active from the control panel on both of the marketplaces I am registered in. No greyed out buttons or anything.

    – I only use one email address for Amazon.

    – I already migrated from AWS last year, when something similar happened to me, and at that time, I think Amazon support did something to solve it. But now “they say” all is working fine.

    I keep on testing, and downloaded the Query monitor plugin https://es.wordpress.org/plugins/query-monitor/

    And effectively, somehow, the API seems to detect that I am reaching the limit. The question is: How is this even possible? Who is making so many calls? Because I don’t think my site should reach that. The 8.000 calls limit are a lot. I have less than 1000 visits each day, and normally, only to one page. (Taking a loot at the

    GET https://webservices.amazon.de/onca/xml
    ?AWSAccessKeyId=AKIAJZPP6EEFFZMLQ6WQ
    &AssociateTag=lasavedetai02-21
    &IdType=ASIN
    &ItemId=B01M5EE52Y%2CB01CZERZ2E%2CB01M029LF5%2CB01CZERZ4M%2CB01CZERZ88%2CB01CZERZ42%2CB01N3L924A%2CB01CZERZ92%2CB01LXGO6N8%2CB01LY465F5
    &Operation=ItemLookup
    &ResponseGroup=Images%2CItemAttributes%2COfferFull
    &Service=AWSECommerceService
    &Timestamp=2019-01-29T17%3A59%3A39Z
    &Version=2013-08-01
    &Signature=6DZh6oT2LH86nLye9HxGjmRBqkiziF2QlQK2czs9quE%3D
    503 Service Unavailable-
    HTTP API Transport: curl
    DNS Resolution Time: 0,0304
    Connection Time: 0,0614
    Transfer Start Time (TTFB): 0,1719
    Response Size: 355 B
    Response Content Type: text/html
    IP Address: 52.94.216.120

    the_content()
    wp-includes/post-template.php:240
    apply_filters(‘the_content’)
    wp-includes/plugin.php:203
    do_shortcode()
    wp-includes/shortcodes.php:197
    preg_replace_callback()
    wp-includes/shortcodes.php:319
    do_shortcode_tag()
    wp-includes/shortcodes.php:319
    AmazonAssociatesLinkBuilder\s\Shortcode_Loader->amazon_link_shortcode_callback()
    wp-content/plugins/amazon-associates-link-builder/shortcode/shortcode_loader.php:52
    AmazonAssociatesLinkBuilder\s\Shortcode_Manager->render()
    wp-content/plugins/amazon-associates-link-builder/shortcode/shortcode_manager.php:111
    AmazonAssociatesLinkBuilder\s\Shortcode_Manager->render_shortcode()
    wp-content/plugins/amazon-associates-link-builder/shortcode/shortcode_manager.php:159
    AmazonAssociatesLinkBuilder\c\Display_Unit_Cache_Loader->get()
    wp-content/plugins/amazon-associates-link-builder/cache/display_unit_cache_loader.php:61
    AmazonAssociatesLinkBuilder\c\Display_Unit_Cache_Loader->create_cache_entry()
    wp-content/plugins/amazon-associates-link-builder/cache/display_unit_cache_loader.php:87
    AmazonAssociatesLinkBuilder\c\Item_Lookup_Response_Cache_Loader->get()
    wp-content/plugins/amazon-associates-link-builder/cache/item_lookup_response_cache_loader.php:59
    AmazonAssociatesLinkBuilder\c\Item_Lookup_Response_Cache_Loader->create_cache_entry()
    wp-content/plugins/amazon-associates-link-builder/cache/item_lookup_response_cache_loader.php:135
    AmazonAssociatesLinkBuilder\i\Item_Lookup_Response_Manager->get_response()
    wp-content/plugins/amazon-associates-link-builder/includes/item_lookup_response_manager.php:93
    AmazonAssociatesLinkBuilder\i\Remote_Loader->load()
    wp-content/plugins/amazon-associates-link-builder/includes/remote_loader.php:41
    AmazonAssociatesLinkBuilder\i\Remote_Loader->fetch()
    wp-content/plugins/amazon-associates-link-builder/includes/remote_loader.php:56
    Plugin: amazon-associates-link-builder 35 0,172

    Ok, that was somehow strange too. I had configured my default marketplace as Spain, and it connected anyway to check at webservices.amazon.de.

    I changed the API keys just in case, with ones I created today from the German Control panel, changed the default marketplace to german. And it is the same anyway:

    (And, I should say, this worked at least from january bis december in 2018)

    Method, URL, Status, Caller, Component, Timeout, Time
    GET https://webservices.amazon.de/onca/xml
    ?AWSAccessKeyId=KIAJ3HD4A2ICM7TQCQQ
    &AssociateTag=lasavedetai02-21
    &IdType=ASIN
    &ItemId=B07G4DMX15
    &Operation=ItemLookup
    &ResponseGroup=Images%2CItemAttributes%2COfferFull
    &Service=AWSECommerceService
    &Timestamp=2019-01-29T18%3A47%3A43Z
    &Version=2013-08-01
    &Signature=xxqFGA%2FLahUEs4BBjkJbeHCUmCzSmL3nLus%2FaRhUX%2B4%3D
    503 Service Unavailable-
    HTTP API Transport: curl
    DNS Resolution Time: 0,0042
    Connection Time: 0,0434
    Transfer Start Time (TTFB): 0,1805
    Response Size: 355 B
    Response Content Type: text/html
    IP Address: 52.94.218.55

    the_content()
    wp-includes/post-template.php:240
    apply_filters(‘the_content’)
    wp-includes/plugin.php:203
    do_shortcode()
    wp-includes/shortcodes.php:197
    preg_replace_callback()
    wp-includes/shortcodes.php:319
    do_shortcode_tag()
    wp-includes/shortcodes.php:319
    AmazonAssociatesLinkBuilder\s\Shortcode_Loader->amazon_textlink_shortcode_callback()
    wp-content/plugins/amazon-associates-link-builder/shortcode/shortcode_loader.php:66
    AmazonAssociatesLinkBuilder\s\Shortcode_Manager->render()
    wp-content/plugins/amazon-associates-link-builder/shortcode/shortcode_manager.php:111
    AmazonAssociatesLinkBuilder\s\Shortcode_Manager->render_shortcode()
    wp-content/plugins/amazon-associates-link-builder/shortcode/shortcode_manager.php:159
    AmazonAssociatesLinkBuilder\c\Display_Unit_Cache_Loader->get()
    wp-content/plugins/amazon-associates-link-builder/cache/display_unit_cache_loader.php:61
    AmazonAssociatesLinkBuilder\c\Display_Unit_Cache_Loader->create_cache_entry()
    wp-content/plugins/amazon-associates-link-builder/cache/display_unit_cache_loader.php:87
    AmazonAssociatesLinkBuilder\c\Item_Lookup_Response_Cache_Loader->get()
    wp-content/plugins/amazon-associates-link-builder/cache/item_lookup_response_cache_loader.php:59
    AmazonAssociatesLinkBuilder\c\Item_Lookup_Response_Cache_Loader->create_cache_entry()
    wp-content/plugins/amazon-associates-link-builder/cache/item_lookup_response_cache_loader.php:135
    AmazonAssociatesLinkBuilder\i\Item_Lookup_Response_Manager->get_response()
    wp-content/plugins/amazon-associates-link-builder/includes/item_lookup_response_manager.php:93
    AmazonAssociatesLinkBuilder\i\Remote_Loader->load()
    wp-content/plugins/amazon-associates-link-builder/includes/remote_loader.php:41
    AmazonAssociatesLinkBuilder\i\Remote_Loader->fetch()
    wp-content/plugins/amazon-associates-link-builder/includes/remote_loader.php:56
    Plugin: amazon-associates-link-builder 35 0,180

    ya has logrado resolver el problema yo sigo son poder mostrar los productos 🙁

    It still doesn’t work. 🙁

    hi Taisa, are you sure you weren’t cut off with the 1/23 change that Amazon just implemented. I am pretty sure that is my problem. Amazon doesn’t like small businesses. I guess they forgot when they were small… or maybe they were never small 🙂

    ps. they also make it sound easy to ‘just add a new tag’. i’m on wordpress.com so i don’t have access to the backend to do a global change to my posts and pages, so i do each individually. it took me hours to change canada, only to have it cut off right after i finished everything. it probably took me days just for that change. i’m pretty done with amazon, it’s just not worth all the hard work. i’d rather put that effort into SEO fixes and content. but that’s probably just me…

    🙂 I hope you figure this out and i sincerely hope it’s not an api id change!

    My problems started in December, so I don’t know if it is related with the 23/1 change. And it can’t be that they blocked me, because I can use the same configuration, keys, id, etc. in other domains… but not in mine. So it must be something else, the API answers a code as if I reached the limit (more than 1 call per second, or more than 8.000 calls a day). I have some sales this month, so I should have access (and of course I have access, but not from my domain).

    I repeat, when a EXACT clone of my domain worked… I don’t think I am the problem.

    Why don’t I have access? Nobody knows and nobody is able to help me.

    My theories now:
    – One of the plugins is doing lots of calls when it shouldn’t and wasting my “limit” very fast. So… I lost access.
    – Or maybe, because I didn’t have sales on Germany this last month (yeah, because the plugin stopped working I guess, and I have less SEO traffic from here). But I don’t think that should work like this, because I tried too using the spanish API and have sales there. (But this don’t explain too why from other domains work).

    Ok, I’ve got an answer from Amazon Support.

    “He comprobado y en nuestro sistema todo es normal. El problema debe llegar del plugin que utilices por lo que te aconsejo conectar con el suporte del plugin que usas y ellos deben ayudarte con eso.”

    So, I should get some help HERE. Please? What is happening?

    aún sin resolver nada, no responden cuando piden las características de php, wordpress, etc, entonces para que las piden.

    Bueno, pues “ahora mismo” sí me ha vuelto a funcionar, pero no sé si durará. ¿Por qué? Quién sabe después de todo lo que he ido probando…

    Aunque decir que lo último que hice fue ayer activar el sistema de caché de otro de los plugins de enlaces que utilizo (cosa que el oficial no tiene, por cierto)… Y también hablar con mi hosting. Así que aún no sé si es permanente y seguirá funcionando, o si volverá a fallar, ni qué lo arregló exactamente.

    ***
    Well, “right now” has returned to work for me, but I don’t know if it will last. Why? Who knows after all what I’ve been trying …

    Although to say that the last thing I did yesterday was to activate the cache system of another of the link plugins I use (which the officer does not have, by the way) … And also talk to my hosting. So I still do not know if it is permanent and will continue to work, or if it will fail again, or what exactly fixed it.

    Ok, now I tried with the query monitor in a page with many links, because some still didn’t show, and shows the same 503 error as before. I think because “the calls are going out too quick”. I think you should solve this, and make the plugin wait and show the images later or something.

    Also, why not having a cache or something, so it doesn’t make so many calls? We need this to work better, and not fail so much, please.

    And, as I already said before, it would be nice that the “basic product links” don’t need an API call to be created. You already have the ASIN and the id. If the product is not available anymore, it would take to a “not found” page and that is not a problem, but it will not waste a “call”.

    Also, now the search doesn’t work. It says I am doing the calls too quick… again. I think this worked only for a short time. And it will be again like before in a few moments.

    con qué plugin de cache lo lograste?, a mi me sigue sin funcionar. 🙁

Viewing 15 replies - 16 through 30 (of 41 total)
  • The topic ‘Links and images doesn’t show at backend’ is closed to new replies.