# \[WS\] vgmdb

**URL:** https://community.mp3tag.de/t/ws-vgmdb/9731
**Category:** Web Sources Scripts
**Created:** [January 19, 2010, 12:25pm UTC](https://community.mp3tag.de/t/ws-vgmdb/9731 "2010-01-19T12:25:18Z")
**Posts on this page:** 1
**Showing post:** 171

<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: [March 19, 2024, 8:56am UTC](https://community.mp3tag.de/t/ws-vgmdb/9731/171 "2024-03-19T08:56:28Z")

</div>

VGMdb changed their index html. If the query entry finds the exact album, it appears that vgmdb automatically redirects to the album page. I've been updating the index portion of the vgmdb web source, but mp3tag does not seem to handle redirects well. MP3Tag's debug log, strangely, does not update such redirects, so I cannot update the websource to handle such events. Before, I had the index portion setup to handle album hits with CurrentURL, such as:

`[IndexFormat]=%Catalog%|%_url%|%Album%|%Year%|%TYPE%`

Code:

```auto
findline "<tr rel='rel_invalid" 1 1
ifnot "<tr rel"
	say "|"
	sayoutput "CurrentURL"
	say "|"
	say "|"
	say "|"
	exit
endif

```

But I've been getting the following for direct hits:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/b/1/b1aee1db1131383e78139cbcd1bda7099988c4d2.png)

More generic search queries still work however.

---

_[View the full topic](https://community.mp3tag.de/t/ws-vgmdb/9731)._