# Third parameter broken for the regexpreplace fn

**URL:** https://community.mp3tag.de/t/third-parameter-broken-for-the-regexpreplace-fn/61653
**Category:** Web Sources Discussion
**Created:** [July 23, 2023, 10:25pm UTC](https://community.mp3tag.de/t/third-parameter-broken-for-the-regexpreplace-fn/61653 "2023-07-23T22:25:29Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [July 25, 2023, 10:50am UTC](https://community.mp3tag.de/t/third-parameter-broken-for-the-regexpreplace-fn/61653/7 "2023-07-25T10:50:36Z")

</div>

> [@stevehero](#):
>
> So not sure how they even worked in the first place.

I've checked this further and I had a one-off error in validating the function parameters in web sources scripts, so that those would never be checked.

With the latest additions I needed to extend the maximum number of parameters per function from 3 to 5, so that the 3rd parameter was now checked too. We also had this before in our conversation via PM where the superfluous parameter for `debug` suddenly caused problems.

To make life easier for all of us, I've now extended validation and also added reporting of syntax errors via an error message with [Mp3tag v3.21c](https://community.mp3tag.de/t/455).

---

_[View the full topic](https://community.mp3tag.de/t/third-parameter-broken-for-the-regexpreplace-fn/61653)._