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

[Groupings] Content is not saved #6360

Closed
MalwareCantFly opened this issue Mar 14, 2024 · 2 comments · Fixed by #6641
Closed

[Groupings] Content is not saved #6360

MalwareCantFly opened this issue Mar 14, 2024 · 2 comments · Fixed by #6641
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@MalwareCantFly
Copy link

Description

Groupings -> Content:
Adding content and hiting the save button, doesn't do anything.

Environment

Demo environement

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to a specific grouping
  2. Click the Content tab
  3. Edit the content and hit the save button
  4. Exit the content tab, and come back to it
  5. There is no content

Expected Output

Content should be saved :)

Thanks!

@MalwareCantFly MalwareCantFly added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 14, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.8 milestone Mar 15, 2024
@SamuelHassine SamuelHassine removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 15, 2024
@labo-flg labo-flg self-assigned this Mar 18, 2024
@labo-flg
Copy link
Member

Cannot edit the main content + adding files fail too.

@Kedae
Copy link
Member

Kedae commented Mar 19, 2024

Linked to #6379

@Jipegien Jipegien modified the milestones: Release 6.0.8, Release 6.0.9 Mar 20, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.9, Release 6.0.10, Release 6.1.0 Apr 3, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants