# All navigation buttons broken

**URL:** <https://connect.superhuman.com/t/all-navigation-buttons-broken/19250>\
**Category:** Ask the Community\
**Created:** [October 30, 2020, 2:19am UTC](https://connect.superhuman.com/t/all-navigation-buttons-broken/19250 "2020-10-30T02:19:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brendan\_Woithe](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/brendan_woithe/32/11353_2.png) [@Brendan\_Woithe](https://connect.superhuman.com/u/Brendan_Woithe)\
**Post date:** [October 30, 2020, 2:19am UTC](https://connect.superhuman.com/t/all-navigation-buttons-broken/19250/1 "2020-10-30T02:19:44Z")

</div>

Hi,  
People using our documents have just noticed that all our buttons in our doc that take the user to different sections are no longer working.  
An example formula being used inside te button is  
OpenWindow(“dpnJ-AdvWke/Projects-About\_suX\_c#UX-Menu-Projects\_tuHRS/”)  
In the past, this would stay in the current browser tab and open the correct section.  
Now it opens a new browser tab and (rightly) throws up a browser error.

Has something changed on the back end for coda that would cause this issue?

What would you suggest we do to fix it?

EDIT : Just saw this in the bugs section…but I’m don’t think this is related to what I’m seeing

> [@Openwindow (url(xxxx)) not working anymore since today?](https://connect.superhuman.com/t/openwindow-url-xxxx-not-working-anymore-since-today/11107/4):
>
> Anchor links in a canvas haven’t been 100% supported. You can definitely jump to a table, but not necessarily other parts of the canvas. We would like to support this more fully, but it hasn’t been sorted out yet. The url has the info needed, but the actual anchor link html isn’t all there.

What I’m guessing has changed is the way coda allows you to use just part of the URL in the past. This was great, as the same buttons could be used in a published doc or in the edit doc (which would have different front parts of the URL)

Or is there something else at play?

Is it better to use the hyperlink formula? (But that’s not a drop-in replacement either AFAIK)

Any help is much appreciated.

---

<div class="post-metadata">

**Author:** ![Ben\_Lee](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/ben_lee/32/49867_2.png) [@Ben\_Lee](https://connect.superhuman.com/u/Ben_Lee)\
**Post date:** [October 30, 2020, 7:31pm UTC](https://connect.superhuman.com/t/all-navigation-buttons-broken/19250/2 "2020-10-30T19:31:57Z")

</div>

I tested this in Chrome with the following formula setup and it worked.

`Concatenate(thisDocument.Url(),"/[PAGE ID]").Hyperlink()`

[PAGE ID] is just the `_xxxxx` after the page name in the URL.

---

<div class="post-metadata">

**Author:** ![Brendan\_Woithe](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/brendan_woithe/32/11353_2.png) [@Brendan\_Woithe](https://connect.superhuman.com/u/Brendan_Woithe)\
**Post date:** [November 2, 2020, 11:58pm UTC](https://connect.superhuman.com/t/all-navigation-buttons-broken/19250/3 "2020-11-02T23:58:02Z")

</div>

> [@Ben\_Lee](#):
>
> Concatenate(thisDocument.Url(),“/[PAGE ID]”).Hyperlink()

Thanks. I’ve managed to find all the buttons / change all my formulas. Working again.  
Still doesn’t explain why it worked for 9 months and then suddenly stopped.