- Affected version
- 2.3.13
In
For the conversations/direct messages rebuild, for example, this will output
In
As a result, the
This can be confusing when monitoring an Atomic job (for example, triggered after an import) that includes both jobs as the distinct steps have duplicated status messages to earlier steps, each with their own progress output.
This affects multiple content types.
src/XF/Job/AbstractRebuildJob.php the getStatusMessage method reads like this:
PHP:
public function getStatusMessage()
{
$actionPhrase = \XF::phrase('rebuilding');
$typePhrase = $this->getStatusType();
return sprintf('%s... %s (%s)', $actionPhrase, $typePhrase, $this->data['start']);
}
For the conversations/direct messages rebuild, for example, this will output
Rebuilding... Direct messages.In
src/XF/Job/ConversationEmbedMetadata.php the getActionDescription method reads like this:
PHP:
protected function getActionDescription(): string
{
$rebuildPhrase = \XF::phrase('rebuilding');
$type = \XF::phrase('direct_messages');
return sprintf('%s... %s', $rebuildPhrase, $type);
}
As a result, the
ConversationEmbedMetadata job will also output Rebuilding... Direct messages.This can be confusing when monitoring an Atomic job (for example, triggered after an import) that includes both jobs as the distinct steps have duplicated status messages to earlier steps, each with their own progress output.
This affects multiple content types.