Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

"recent deletions" moderator tool produces error

+2
−0

The "recent deletions" link under mod tools is consistently returning a 500 server error for me. One reference: 2ba998b1-84b1-4675-aeb8-bebcf3465b5f

I've tried this on two sites. It's been a few days since I last accessed this tool anywhere, so I can't pin down when this behavior might have started.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (1 comment)

1 answer

+3
−0

Oooh. This looks like a funny issue.

As far as I can tell, there are two levels here:

  1. The error page contains an entry for a help center article. This isn't supposed to happen and is likely a data error. We (read: ArtOfCode) have to look at the database, whether there is somewhere an article wrongly marked as deleted.

  2. There is a naming issue with the view files. The post list attempts to reach a partial called posts/document, which would be located at app/views/posts/_document.html.erb. However, such a file doesn't exist. We only have app/views/posts/document.html.erb (mind the missing underscore). And that isn't even the file we want to show. So we should likely create an other partial and use it there. Or we could probably just assume, that this case is never needed and should not occur in production.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

General comments (1 comment)

Sign up to answer this question »