When Batch ID doesn't exist, Drupal should emit a 404

Created on 3 May 2013, over 11 years ago
Updated 16 January 2023, almost 2 years ago

Problem/Motivation

Currently if you try to go to /batch?id=123 you get redirected to the homepage with a message stating "No active batch".

Proposed resolution

Since the batch doesn't exist Drupal should just emit a 404 instead.
Display an error message to the user.

Remaining tasks

  • Update the error message: see Comment #187.
  • Update the "after" screenshot in the issue summary.

User interface changes

Error message displayed, "The requested batch ({ID}) could not be found."

Before

After

API changes

If you try to go to /batch?id=123 Drupal emit a 404.

🐛 Bug report
Status

Needs work

Version

10.1

Component
Batch 

Last updated 4 days ago

Created by

🇺🇸United States timaholt

Live updates comments and jobs are added and updated live.
  • Documentation

    Primarily changes documentation, not code. For Drupal core issues, select the Documentation component instead of using this tag. In general, component selection is preferred over tag selection.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024