Issue Bug Closed

#92428redirects:checkintegrity command fails when saving again without a site identifier

Daniel Siepmann 09/28/20, 08:31 updated 12/22/20, 11:05

Description

When creating a scheduler task for “redirects:checkintegrity” and saving it again without providing a site identifier, an empty string will be saved.

The code expects either null for no site, or an string with identifier of a single site.

This leads to the following failure during execution:

 [WARNING] No site found for identifier                                        

Reviews 2