# 2.69 has broken Amazon source

**URL:** https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698
**Category:** Web Sources Discussion
**Created:** [March 15, 2015, 6:57pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698 "2015-03-15T18:57:59Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Alcahest](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/8491ac/32.png) [@Alcahest](https://community.mp3tag.de/u/Alcahest)
#### Post date: [March 15, 2015, 6:57pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/1 "2015-03-15T18:57:59Z")

</div>

Hey all,  
Just installed v2.69 and it seems the update to the Amazon.com.src has broken it completely.  
Whatever I input, album name, artist name, catalog #, I'm always getting the error:

* * *

## Mp3tag v2.69

## Sorry, no entries are matching your search criteria.

## OK

I tried with super obvious stuff like "madonna", etc.. not once was it able to output anything other than the error above.  
Thanks for any help.

Edit: reverting to the old script from 2.68 fixes the issue..

Edit2: well that was easy, re-adding "AssociateTag=mp3tag-20&" to the 2.69 script fixes the issue as well.. why was that removed?

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [March 15, 2015, 7:05pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/2 "2015-03-15T19:05:51Z")

</div>

> [@Alcahest](#):
>
> ... to the Amazon.com.src has broken it completely.  
> ...

I can confirm that the tag search at [amazon.com](http://amazon.com) does not return any results.  
The cover search works for [amazon.com](http://amazon.com) and [amazon.de](http://amazon.de)  
The search at [amazon.de](http://amazon.de) works for both.

---

<div class="post-metadata">

### Author: ![Alcahest](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/8491ac/32.png) [@Alcahest](https://community.mp3tag.de/u/Alcahest)
#### Post date: [March 15, 2015, 7:09pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/3 "2015-03-15T19:09:15Z")

</div>

> [@ohrenkino](#):
>
> I can confirm that the tag search at [amazon.com](http://amazon.com) does not return any results.  
> The cover search works for [amazon.com](http://amazon.com) and [amazon.de](http://amazon.de)  
> The search at [amazon.de](http://amazon.de) works for both.

I edited my post with the fix ohrenkino.  
Just change:

```
http://webservices.amazon.com/onca/xml?Service=AWSECommerceService&Operation=

```

to

```
http://webservices.amazon.com/onca/xml?Service=AWSECommerceService&AssociateTag=mp3tag-20&Operation=

```

What I wonder is why was that altered..?

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 16, 2015, 8:03am UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/4 "2015-03-16T08:03:52Z")

</div>

This change slipped through by accident.

> [@Alcahest](#):
>
> What I wonder is why was that altered..?

[Amazon.com](http://Amazon.com) terminated my associates account because they were interpreting the clicks users of Mp3tag make via the tag sources dialog (via the This album on [Amazon.com](http://Amazon.com) link) as artificially generated clicks (which is of course not the case). They told me to not use the associate tag anymore and I made some experiments to remove it but still leave the web source intact.

I guess I have to release another new version which fixes this.

Thanks!

Florian

---

<div class="post-metadata">

### Author: ![Alcahest](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/8491ac/32.png) [@Alcahest](https://community.mp3tag.de/u/Alcahest)
#### Post date: [March 16, 2015, 9:03pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/5 "2015-03-16T21:03:14Z")

</div>

> [@Florian](#):
>
> This change slipped through by accident.
> 
> [Amazon.com](http://Amazon.com) terminated my associates account because they were interpreting the clicks users of Mp3tag make via the tag sources dialog (via the This album on [Amazon.com](http://Amazon.com) link) as artificially generated clicks (which is of course not the case). They told me to not use the associate tag anymore and I made some experiments to remove it but still leave the web source intact.
> 
> I guess I have to release another new version which fixes this.
> 
> Thanks!
> 
> Florian

Thanks for this detailed explanation Florian, makes sense now.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 23, 2015, 6:53pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/6 "2015-03-23T18:53:02Z")

</div>

Thanks again for pointing!

I've fixed the issue with the current Development Build (v2.69a) available from [http://developer.mp3tag.de](http://developer.mp3tag.de)

Kind regards  
Florian

---

<div class="post-metadata">

### Author: ![Alcahest](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/8491ac/32.png) [@Alcahest](https://community.mp3tag.de/u/Alcahest)
#### Post date: [March 23, 2015, 8:14pm UTC](https://community.mp3tag.de/t/2-69-has-broken-amazon-source/16698/7 "2015-03-23T20:14:58Z")

</div>

You're more than welcome 😉  
Thanks for the headsup!
