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.

Sign up for GitHub

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

Jump to bottom

Topic creation returns 500er #969

Open
janz93 opened this issue Dec 12, 2022 · 4 comments
Open

Topic creation returns 500er #969

janz93 opened this issue Dec 12, 2022 · 4 comments
Labels
bug

Comments

@janz93
Copy link
Member

janz93 commented Dec 12, 2022

Hello everyone

after submitting a topic from the website or the admin panel the page returns the rails 500er page.

image
@janz93 janz93 added the bug label Dec 12, 2022
@janz93 janz93 changed the title Topic creation return 500er Topic creation returns 500er Dec 12, 2022
@phoet
Copy link
Member

phoet commented Dec 13, 2022

there is a unique constraint on the event name

@salzig
Copy link
Collaborator

salzig commented Aug 15, 2024

maybe duplicate of #798

@JoschkaSchulz
Copy link
Member

JoschkaSchulz commented Oct 1, 2024 •
edited
Loading

@phoet would it be possible to add @salzig and me to Appsignal? There is an Appsignal right? I would like to hunt this exactly bug because it drives me crazy while using the admin interface :D (Also seems not a duplicate @salzig the bug still exists)

JoschkaSchulz added a commit that referenced this issue Oct 1, 2024
@JoschkaSchulz
fix(#969): changed administrate api
0999001 
After saving an event an error will show up. This error happens on the
show page of the event. It seems like the administrate api has changed
and the attributes are now nested inside a hash with no given key.

This commit returns the correct attributes for the show page and
resolves the attributes correctly.
@JoschkaSchulz
Copy link
Member

ah sorry. I just thought it would be the same error as on the events page but this one was already resolved by @salzig and the fix worked fine... we had also another error that I fixed in the #1053

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@phoet @salzig @JoschkaSchulz @janz93