Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Presentation Button Link keeps old values #7942

Closed
3 tasks done
nathanhere opened this issue Sep 9, 2021 · 2 comments
Closed
3 tasks done

Presentation Button Link keeps old values #7942

nathanhere opened this issue Sep 9, 2021 · 2 comments

Comments

@nathanhere
Copy link

nathanhere commented Sep 9, 2021

Preflight Checklist

Describe the Bug

The Presentation button link seems to keep old url values, even when deleted and replaced. This behavior didn't seem to be present in prior versions. In prior versions, new collection items were created with correctly updated presentation button links, however, I noticed in RC 92 version that all subsequent items that were created contain the old url value.

To Reproduce

  1. Create presentation button link, fill out url field, save.
  2. Create a new item in the corresponding collection.
  3. Delete presentation button link from the collection data model.
  4. Create a new presentation button link with a different url value.
  5. Create a new item in the corresponding collection.
  6. Click or hover over the button and observe that it still holds the old value.

What version of Directus are you using?

RC92

What version of Node.js are you using?

14.17.4

What database are you using?

Postgres 13

What browser are you using?

Chrome

What operating system are you using?

MacOS

How are you deploying Directus?

Docker Compose

@rijkvanzanten
Copy link
Member

When you say

Create a new presentation button link with a different url value.

Did you use the same field name for the presentation button? 🤔 Wondering where this overlap is coming from

@nathanhere
Copy link
Author

nathanhere commented Sep 10, 2021

My apologies. After more digging, I've found that the issue is that I thought a collection item's field that used a default value (which I used as a templating variable in the button link) would update if the default field value was changed in the data model. Further complicating this was that I marked the field as hidden, so the issue wasn't immediately obvious to me.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants