# \[WS\] Discogs (pone mod)

**URL:** https://community.mp3tag.de/t/ws-discogs-pone-mod/9226
**Category:** Broken Web Sources
**Created:** [October 29, 2009, 3:18am UTC](https://community.mp3tag.de/t/ws-discogs-pone-mod/9226 "2009-10-29T03:18:24Z")
**Posts on this page:** 1
**Showing post:** 933

<div class="post-metadata">

### Author: ![ms6676749](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/b4bc9f/32.png) [@ms6676749](https://community.mp3tag.de/u/ms6676749)
#### Post date: [September 5, 2024, 3:25pm UTC](https://community.mp3tag.de/t/ws-discogs-pone-mod/9226/933 "2024-09-05T15:25:44Z")

</div>

Yup, recent changes to discogs' API json output has broken pone's discog mod for good. I looked over pone mod and it is a rat's nest of regex's. Credit to pone for untangling that json mess from discogs. Despite liking regex myself, I'm not going dive in debug regex's other than my own. Sadly, this means that I had to retire my heavily modified discogs pone mod.

Afterwards, I modified @Florian's json-based discogs websource that comes with the mp3tag install (a mix between parsing discogs' json output for per track data and using regex for credits and notes information), some of which I shared here: [Discogs (pone mod) no longer works - #10 by ms6676749](https://community.mp3tag.de/t/discogs-pone-mod-no-longer-works/65730/10)

Unfortunately, my tag preferences deviate from pone mod a little bit.

---

_[View the full topic](https://community.mp3tag.de/t/ws-discogs-pone-mod/9226)._