Fixed XF\Job\Manager::enqueueLater no longer accepts null for $uniqueId argument

[Xon]

Affected version

2.3.3

public function enqueueLater(string $uniqueId, int $runTime, string $jobClass, array $params = [], bool $manual = false, int $priority = 100): ?int

$uniqueId used to accept null. Thankfully an empty string works the same.

(This affects XenForo 2.2.16 too)

 

[XF Bug Bot]

Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.3.4).

Change log:

Allow `null` unique ID when enqueuing a job later

There may be a delay before changes are rolled out to the XenForo Community.