Status message does not appear after running /core/rebuild.php

Created on 22 December 2020, over 4 years ago

Updated 20 March 2023, about 2 years ago

Problem/Motivation

As per the docs running Rebuild.php script can clear Drupal cache even when Drupal itself does not work. On running it from browser It does clears the cache but as written in the code \Drupal::messenger()->addStatus('Cache rebuild complete.'); of the script it doesn't shows the status message "Cache rebuild complete."

Steps to reproduce

Add $settings['rebuild_access'] = TRUE; in your settings.php file.
Browse the url /core/rebuild.php
It redirects to home page after clearing the cache but doesn’t shows any status message.

Proposed resolution

Either remove the message or handle the redirection with different ways.

Remaining tasks

None

User interface changes

None

API changes

None

Data model changes

None

Release notes snippet

None

🐛 Bug report

Status

Closed: duplicate

Version

10.1 ✨

Component

Other →

Last updated about 10 hours ago

Created by

🇮🇳India saxenaakansha30 New Delhi, India

Live updates comments and jobs are added and updated live.

Bug Smash Initiative

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment about 2 years ago →
🇦🇺Australia mstrelan
Tested this on 10.1.x and can confirm the issue still exists. One possible solution would be to define a route and controller that simply sets the message and performs the redirect, then rebuild.php can redirect to that route. That seems like overkill though, and I'm sure there is a simpler way.
Status changed to Closed: duplicate about 2 years ago11:28pm 20 March 2023
Comment about 2 years ago →
🇦🇺Australia mstrelan
I came across 🐛 Messenger service can't set messages super early and loses reference to flashbag reference on rebuild Needs review which sounded related. Re-rolled the patch for that issue and tested this again and it was fixed. Marking as a duplicate of that issue.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024