Only to remove/add # in the USER OPTIONS section. I'm going to perform a clean install of MP3TAG and the scripts and see what results I get.
1 Like
Do a portable one and test it that way.
1 Like
I'm using v6.0 2023.07.19 with the same Mp3tag version.
Edited this reply. A standalone clean install exhibits the same problem for that example track. NO accurate results given for those search terms, yet removing the release name returns numerous results with the correct result in the top spot.
hi guys!
is something wrong with beatport?
i was tagging some releases and suddendly i'm getting this error
I tried previous links that i used to tag some releases 10minutes ago and they arent workin anymore too.
Theres ppl with the same issue?
Oh yes, that's exactly what I'm getting. I thought I had broken something with my clean install, but perhaps there is a global issue. It seems to have now been fixed.
After clean standalone install of MP3TAG, and clean install of Beatport WSS, I continue to get the same issues described above. Screen capture of the behavior: Beatport WSS Results - YouTube
i've turned ON VPN and seems to be workin fine now 
Edit: down again... 
Strange... Nothing works anymore. 
1 Like
It seems like the script doesn't use a separator character for the two search values, e.g., + which results in a search query like Alex StealthyOnce instead of Alex Stealthy Once. Maybe @stevehero can change the %s to +%s for the "Release" search field definition.
It might be due to some changes on Beatport's side, where the initial non-JSON block of the response now spans multiple lines.
An initial JoinUntil "application/json" should do the trick.
3 Likes
I'll get fixing that later this evening. Thanks for checking this.
3 Likes
Confirmed - many thanks again!
(Added it before these lines:
RegexpReplace "<!DOCTYPE\s+.+?json">" "" # Remove before JSON
RegexpReplace ".+?" "" # Remove after JSON)
EDIT: Sorry, but this only brings up the search result list. As soon as I double-click on an entry the "Sorry, no entries are matching your search criteria" error message appears.
2 Likes
You'd also need to add this line to the [ParserScriptAlbum] section of the WSS.
2 Likes
Yes, that did the trick.
1 Like
Hi Florian,
While investigating this, I was trying to find a method to diagnose what is going on here, but couldn't find any log, or other mechanism to see what query actually gets sent to the source server. Does such a mechanism exist?
Yes, please see the Debugging section at Developing Tag Sources – Mp3tag Documentation
The debug output has a list of all collected values at the end of the file, where CurrentUrl denotes the URL that is used for the query.
And just in case you really want to go down that rabbit hole, please use Web Sources Discussion for further questions that are not directly related to the Beatport WS.
2 Likes
A post was split to a new topic: Download previous version v3.21b
v6.002 2023.08.02
- ADDED: Option to for formatting how Title (feat. Artist) is done so you can do this (The default) Title (feat. artist) => Title feat. artist. See RegexpReplace in options.
- FIX:
%sneeded to be+%sin some .src files. - FIX: Beatport source code now has multiple lines.
JoinUntil "</html>"added. - FIX:
JoinUntil "</html>"and RegexpReplace functions are now positioned just below[ParserScriptAlbum]=...to enable RegexpReplace functions below to work.
6 Likes
Many thanks Steve! 
1 Like
Hi Steve,
Although I do not understand these things, I think there is a small error in the following file;
" Beatport by &stevehero v6#RELEASE Direct by &Www(URL).src"
When I deleted the plus sign (+) in the line below, I was able to get data with the url address;
27# [SearchBy]=RELEASE Direct by www(URL)||$trim($lower($regexp($regexp(%www%,(?i)^www,https://www),\bhttp\b,https,classic.beatport),www.beatport,https://pro.beatport,https://www.beatport))||+%s
Also thank you very much.
1 Like