@stevehero Sorry this doesn't help out.
Sometimes it does, sometimes it doesn't. Bit like real life I suppose 
Sometimes it does, sometimes it doesn't.
I noticed the same Steve. It's okay mate, your work is good anyway.
1 Like
@stevehero I hope you are doing good mate.
I need your help to remove the selected tags of the screen,
what need to midify on your script in order those tags not to generated at all?
Thank you
At the bottom of every script there's a few lines:
# set "BEATPORT_ARTIST_URL"
# set "BEATPORT_ITEM_TYPE"
# set "BEATPORT_LABEL_URL"
# set "BEATPORT_RELEASE_ID"
# set "BEATPORT_TRACK_ID"
# set "BEATPORT_TRACK_URL"Change to:
set "BEATPORT_ARTIST_URL"
set "BEATPORT_ITEM_TYPE"
set "BEATPORT_LABEL_URL"
set "BEATPORT_RELEASE_ID"
set "BEATPORT_TRACK_ID"
set "BEATPORT_TRACK_URL"Check the readme file in starting post if you've trouble. 
@stevehero sure, for some reason those line it was missing from my source file, Okay I find out the way 
thanks
Not working script. Help. 500: internal server error
Have you tried visiting the website or goggling a 500 error.
I get the same error as AndreyN. Strangely, this occurs for random searches, i.e. sometimes it works if I manually drop part of the release name and/or author;
Example: Friction, JP Cooper - Dancing Remixes
FAILED: Friction dancing
WORKED: dancing (then manually selecting the correct release from the list
I think this is an issue on BP side, as some of the releases work, while others don't.
Note: I was running mp3tag 2.79, but even updating to 2.89a didn't resolve the issue.
I understand that beatport has disabled the search for the release
on the site like looking for a script error shows
The classic website that the scripts are based on is probably just a html port of the API for the new beatport.com website and some errors may occur. Or the new website may have similar issues.
- yes, sometimes the search needs tweaking.
can you check what's the problem? on a site the classic.beatport finds and through mp3tag an error 500 (Nikolay Mikryukov - Deep Hypnosis,)
or is it a problem on the side of beatport?
I think BP must have changed something as of last Friday, causing the script to no longer be able to access the info parsed via the API. I tried modifying the URL to use the new BP site, but neither pro.beatport nor https://beatport.com seemed to work.
I'm getting the same error: 500 Internal Server error when trying to connect to classic.beatport.com
Haven't used the script in a while. I'l try get round to fixing the issue (if even possible). For now just put those files to the side.. sorry for the inconvience.
Support Beatport
"Hi, We are aware of the search issues with classic.beatport.com and are working on a fix. I recommend using beatport.com for now. Let us know if you have any other issues!"
Yeah, I only done a search there and no beuno. I'm really busy with work atm anyway but it's good to know it's an internal issue.
Thanks for following up on this @AndreyN. The script will work as soon as BP get their 
together. My script pulls all the same info anyway and is virtually bug-free AFAIK.
Please tell me how to change from classic.beatport.com to beatport.com.
Thanks.
Can you be patient? 
It will work eventually.
Of course. Obviously I mis-understood what AndreyN said and thought it was meant for us users.