MediaMonkey forum

I found a webhoster with free webspace and current curl/openssl version.

Please download the updated script here http://www.germanc64.de/mm/DiscogsAutoTagWeb_V5.36a.zip and copy the vbs-file to the script location:
C:\users\YOURUSERNAME\AppData\Roaming\MediaMonkey\Scripts\

Try it and post the result.

Doesn't work here. Still the same error. I must point out, however, that I deleted DiscoGS Tagger entry from my DiscoGS profile, since I starting fresh might fix the error. Still, the script, if working correctly, should add the entry automatically, no?

V5.36a works correctly for me.

Thank you!

Authentication Error with Discogs Tagger 5.3.6

Lately, I encountered an error while searching for tagging Information in discogs database.
After having installed the latest Version (5.3.6) and having granted Access in my discogs Profile, all worked fine for a few weeks.
But suddenly there is a Pop up window in MediaMonkey asking me for authentication procedure at dicogs database - when clicking on "OK", IE browser opens with an error message as follows:

OAuth client error
Error: it was not possible to access the OAuth request token: it was returned an unexpected response status 302 Response:

OAuth client: Checking the OAuth token authorization state
OAuth client: The OAuth access token is not set
OAuth client: Requesting the unauthorized OAuth token
OAuth client: Accessing the OAuth request token at http://api.discogs.com/oauth/request_token
OAuth client: Could not retrieve the OAuth access token. Error: it was not possible to access the OAuth request token: it was returned an unexpected response status 302 Response:


Website URL is : http://www.germanc64.de/mm/oauth/oauth_ ... 6DF4D4F7C8

Usually, I would expect to be directed towards Login @ discogs?

Anyone an idea what goes wrong here?

And YES, I use the latest Version of MediaMonkey and my Profile at discogs Shows that Authentication/Token is granted for discogs tagger.

5.36a not working for me.

I had deleted my oauth token when the problem first happened and before I found this thread so now I need a new token for the script.

The authorisation page still displays the same error as before (302) and looking at the script the authentication routine still points to germanc64.de so I guess this script update will only fix things for people if the script is still authenticated with discogs?

Thanks for the update! It is working again!

I had uninstalled and reinstalled it, and I had also removed the tokens from options and even tried to generate a new one from my account at Discogs (which gives no secret code to go with it, by the way ). I had NOT revoked permission for Discogs tagger at the time in my account.

So I did as instructed above, dropping the script in the scripts directory, and still got the OAuth error. Of course, since the token is wrong. I had backed up the old tokens to my Evernote, so I reentered them as they were before this started and it is now working fine.

Sorry for the problem with the authorize script. Now it should work again.

Just added a new version of the DiscogsTagger. I changed the authorize script to work with HTTPS.

Happy tagging

Works now, thanks!

Working here too.

Thanks for the great extension and keeping it current.

Many many thanks for this, only new to MM but the amazon tagging facilities are pretty sparse, this is just what I needed

Just updated to V.5.38.

The php-files are back on my webspace. I will delete the other free webspace soon, so please update to the new version.

I added a new feature : You can now add the selected album to your discogs collection. Just press the button "Add to user collection" in the Discogs Tagger window.
After that you can find the album in your uncategorized folder at discogs.com. The collections are mainly for selling albums, so it is possible to add an album more than once.
I added a query to check the album (release-number) is not already listed. But you can add the same album with different release-numbers (US-Release, Picture-LP, etc.).
I think, it's a nice feature seeing the albums on discogs you own. And if an album / release got an update (corrected Names, more images, etc.) you receive an email from discogs like this: What do you think about this new feature? Only crap or useful ? Does it works or is it buggy?

Please write me your opinion.

crap_inhuman wrote:Just updated to V.5.38.
You can now add the selected album to your discogs collection.

Pressing the [Add to user collection] button takes about 45 seconds to process; MM remains unresponsive all that time.

crap_inhuman wrote:(...) so it is possible to add an album more than once.

No it's not. After 45 seconds I get a "Release already exists in User Collection" message. - Could be because I have a large collection on Discogs, it's taking so long. I think the script should not check if it's already in the collection (waste of time), just add it.

Anyway this function is not very useful for me, as I manually manage my Discogs collection on the website.

Thanks for the upgrade once more!

Eyal


[Edit, one hour later]
Yes the album was added twice to Discogs' collection, despite the message. Looks like it took some time for Discogs website to reflect the changes.

Eyal wrote:

crap_inhuman wrote:Just updated to V.5.38.
You can now add the selected album to your discogs collection.

Pressing the [Add to user collection] button takes about 45 seconds to process; MM remains unresponsive all that time.

I had known this would happen, but not with the first who test it.
With my 25 test-releases it took 3 seconds..

Eyal wrote:

crap_inhuman wrote:(...) so it is possible to add an album more than once.

No it's not. After 45 seconds I get a "Release already exists in User Collection" message. - Could be because I have a large collection on Discogs, it's taking so long. I think the script should not check if it's already in the collection (waste of time), just add it.

Maybe i should add a switch to turn it off?

Eyal wrote:Anyway this function is not very useful for me, as I manually manage my Discogs collection on the website.

Thanks for the upgrade once more!

Eyal


[Edit, one hour later]
Yes the album was added twice to Discogs' collection, despite the message. Looks like it took some time for Discogs website to reflect the changes.

I just tested the function and didn't find a bug.
I don't want to waste your time, but if you try it again and the same error occur, send me please the last 8 lines (after the line 'Start UserCollection') of the Discogs_Script.log. You can find this file in your scripts-folder of mediamonkey. Thank you !

Hi crap_inhuman,

I'm not criticizing your work by any kind. As I said (last line on my previous post), it's not a bug, it a message (msg_box). There's no error and the script is working well.

crap_inhuman wrote:Maybe i should add a switch to turn it off?

Yes it would be good to not check if it's already in Discogs' collection (DC).

In my case I already know if an album is in my DC because I use the [Song Information Panel] script to display it all in one line. It's an old script but it's working great. It displays all info including the credits.
See http://www.mediamonkey.com/forum/viewto ... =2&t=41882

Discogs Tagger rocks!

Thank you.

Hi Eyal,

thank you for your response.

I thought the script doesn't work correct, cause you wrote

Eyal wrote:No it's not. After 45 seconds I get a "Release already exists in User Collection" message.

and

Eyal wrote:Yes the album was added twice to Discogs' collection, despite the message. Looks like it took some time for Discogs website to reflect the changes.

The album shouldn't added twice, cause the script show the "already exist" message-box. Bug was the wrong word for this, misfunction applies it better.

I add the switch in the next update.

Best wishes,
Sven