GarbageCollectionJob

Extensions can have a construct but don't have too.

Without a construct, it's impossible to create a job in the CMS

Return a signature for this queued job

By default jobs should just go into the default processing queue

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()

Performs setup tasks the first time this job is run.

This is only executed once for every job. If you want to run something on every job restart, use the {@link prepareForRestart} method.

Run when an already setup job is being restarted.

Do some processing yourself!

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

Get a configuration accessor for this class. Short hand for Config::inst()->get($this->class, .....).

Get inherited config value

Gets the uninherited value for the given config option

Update the config value for a given property

An implementation of the factory method, allows you to create an instance of a class

This method will defer class substitution to the Injector API, which can be customised via the Config API to declare substitution classes.

This can be called in one of two ways - either calling via the class directly, or calling on Object and passing the class name as the first parameter. The following are equivalent: $list = DataList::create(SiteTree::class); $list = SiteTree::get();

Creates a class instance by the "singleton" design pattern.

It will always return the same instance for this class, which can be used for performance reasons and as a simple way to access instance methods which don't rely on instance data (e.g. the custom SilverStripe static handling).