# \[SOLVED\] \`relref\` not producing warnings with refLinksErrorLevel = "WARNING"

**URL:** <https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933>\
**Category:** support\
**Created:** [August 29, 2018, 9:49pm UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933 "2018-08-29T21:49:03Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharonl](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/sharonl/32/3236_2.png) [@sharonl](https://discourse.gohugo.io/u/sharonl)\
**Post date:** [August 29, 2018, 9:49pm UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/1 "2018-08-29T21:49:03Z")

</div>

Hi. When I add `refLinksErrorLevel = "WARNING"` to my **config.toml** file (per the [Ref and RelRef Configuration](https://gohugo.io/content-management/cross-references#ref-and-relref-configuration) documentation for this new Hugo v0.45 option), it indeed eliminates the errors for unresolved `relref` link targets, but **I don’t see any warnings for unresolved references** , as I would expect? (The `relref` call doesn’t render any output, which is OK.) The same is true for the `ref` shortcode.

---

<div class="post-metadata">

**Author:** ![maiki](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/maiki/32/16384_2.png) [@maiki](https://discourse.gohugo.io/u/maiki)\
**Post date:** [August 31, 2018, 7:21pm UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/2 "2018-08-31T19:21:53Z")

</div>

Can you share your site’s project? I don’t expect to see any warnings in my site, so I can’t test this.

---

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [August 31, 2018, 7:37pm UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/3 "2018-08-31T19:37:54Z")

</div>

You may find this odd (I kind of agree, but this was done before my time), but you need to run with `hugo -v` to see WARNINGs.

---

<div class="post-metadata">

**Author:** ![sharonl](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/sharonl/32/3236_2.png) [@sharonl](https://discourse.gohugo.io/u/sharonl)\
**Post date:** [September 1, 2018, 8:47am UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/4 "2018-09-01T08:47:52Z")

</div>

Thanks @bep. When using the `--verbose` Hugo CLI option I see `REF_NOT_FOUND` warnings for unresolved `relref` or `ref` calls. Indeed, I find this odd. It would be nice if Hugo could support different verbosity levels.

(@maiki My site doesn’t have unresolved references either. I added local shortcode calls for non-existing link targets just to check the `refLinksErrorLevel` configuration.)

---

<div class="post-metadata">

**Author:** ![sharonl](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/sharonl/32/3236_2.png) [@sharonl](https://discourse.gohugo.io/u/sharonl)\
**Post date:** [September 1, 2018, 9:42am UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/5 "2018-09-01T09:42:29Z")

</div>

@bep Is there a way to identify the current verbosity level from a custom template or shortcode?

---

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [September 1, 2018, 10:50am UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/6 "2018-09-01T10:50:27Z")

</div>

No…

---

<div class="post-metadata">

**Author:** ![maiki](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/maiki/32/16384_2.png) [@maiki](https://discourse.gohugo.io/u/maiki)\
**Post date:** [September 1, 2018, 3:33pm UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/7 "2018-09-01T15:33:33Z")

</div>

> [@sharonl](#):
>
> My site doesn’t have unresolved references either. I added local shortcode calls for non-existing link targets just to check the `refLinksErrorLevel` configuration.

The suggestion stands: please share your project code when seeking help. In this instance you might provide the shortcode to create the errors.

From your perspective you’ve hit a wall in your project, from my perspective you have a complex site that I can’t reproduce easily. That is why we ask.

---

<div class="post-metadata">

**Author:** ![sharonl](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/sharonl/32/3236_2.png) [@sharonl](https://discourse.gohugo.io/u/sharonl)\
**Post date:** [September 1, 2018, 3:49pm UTC](https://discourse.gohugo.io/t/solved-relref-not-producing-warnings-with-reflinkserrorlevel-warning/13933/8 "2018-09-01T15:49:25Z")

</div>

a. We have a proprietary site that I can’t share in its entirety.  
b. In this instance, there was no point in sharing our site, as the problem wasn’t related to any specific implementation. It was a general question of the expected and actual behavior when using the `refLinksErrorLevel = "WARNING"` configuration, which bep was easily able to answer.