- Showcase `<expression>`.
- Explain that unnamed cronjobs are no longer supported.
Deleting unnamed event listeners still is possible to allow for a clean migration of existing listeners.
+#### Cronjob
+
+Installing unnamed cronjobs is no longer supported.
+The `name` attribute needs to be specified for all event listeners.
+
+Deleting unnamed cronjobs still is possible to allow for a clean migration of existing cronjobs.
+
+The cronjob PIP now supports the `<expression>` element, allowing to define the cronjob schedule using a full expression instead of specifying the five elements separately.
+
+
#### Database
The `$name` parameter of `DatabaseTableIndex::create()` is no longer optional.
Provides a human readable description for the administrator.
-### `<start*>`
+### `<expression>`
-All of the five `startMinute`, `startHour`, `startDom` (Day Of Month), `startMonth`, `startDow` (Day Of Week) are required.
-They correspond to the fields in `crontab(5)` of a cron daemon and accept the same syntax.
+The cronjob schedule.
+The expression accepts the same syntax as described in [`crontab(5)`](https://linux.die.net/man/5/crontab) of a cron daemon.
### `<canbeedited>`
<classname>wcf\system\cronjob\ExampleCronjob</classname>
<description>Serves as an example</description>
<description language="de">Stellt ein Beispiel dar</description>
- <startminute>0</startminute>
- <starthour>2</starthour>
- <startdom>*/2</startdom>
- <startmonth>*</startmonth>
- <startdow>*</startdow>
+ <expression>0 2 */2 * *</expression>
<canbeedited>1</canbeedited>
<canbedisabled>1</canbedisabled>
</cronjob>
</import>
-</data>
\ No newline at end of file
+</data>