PublishItemsJob

Defines the title of the job

Return a signature for this queued job

Indicate to the system which queue we think we should be in based on how many objects we're going to touch on while processing.

We want to make sure we also set how many steps we think we might need to take to process everything - note that this does not need to be 100% accurate, but it's nice to give a reasonable approximation

Specifies what user ID should be when running the job valid values: null - (default) - run the job as current user 0 - run the job without a user greater than zero - run the job as a specific user

This is useful in situations like:

• a job needs to always run without a user (like a static cache job)
• a job needs to run as a specific user (for example data migration job)

Note that this value can be overridden in the see QueuedJobService::queueJob()

This is called immediately before a job begins - it gives you a chance to initialise job data and make sure everything's good to go

What we're doing in our case is to queue up the list of items we know we need to process still (it's not everything - just the ones we know at the moment)

When we go through, we'll constantly add and remove from this queue, meaning we never overload it with content

Run when an already setup job is being restarted.

Lets process a single node, and publish it if necessary

Method for determining whether the job is finished - you may override it if there's more to it than just this

Called when the job is determined to be 'complete'

Gets custom config settings to use when running the job.

Sets custom config settings to use when the job is run.

Convenience methods for setting and getting job data

Retrieve some job data