wizhippo/ibexa-scheduled-content

Ibexa DXP scheduled content extension

dev-main 2023-09-15 14:40 UTC

Requires

• php: ^8.1
• doctrine/collections: ^1.6 || ^2.0
• http-interop/http-factory-guzzle: ^1.2
• ibexa/admin-ui: ^4.1
• ibexa/content-forms: ^4.1
• ibexa/core: ^4.1
• ibexa/rest: ^4.1
• ibexa/solr: ^4.1
• lolautruche/ez-core-extra-bundle: ^4.0
• pagerfanta/pagerfanta: ^2.7 || ^3.5
• symfony/translation-contracts: ^2.5 || ^3.0
• twig/twig: ^3.3

Requires (Dev)

• phpstan/phpstan: ^1.1
• phpstan/phpstan-phpunit: ^1.0
• phpstan/phpstan-strict-rules: ^1.0
• phpstan/phpstan-symfony: ^1.0
• phpunit/phpunit: ^9.5
• symfony/proxy-manager-bridge: ^5.4
• symfony/var-dumper: ^5.4

GPL-2.0-only

• Wizhippo

• ibexa

README

Wizhippo Scheduled Content Bundle is an Ibexa Platform bundle to allow scheduling actions on content.

Allows you to publish content as hidden, then create a schedule of actions.

Supported actions are:

• show
• hide
• trash

Actions on unpublished content (such as trashed) are not performed and are marked as evaluate. This means that if content is restored, the unperformed actions will not ben run, but future actions will.

If the schedule command runs such that enough time elapses and multiple actions for the same content are pending, the pending actions are performed in oldest to newest order.

The command wzh:schedule-content is marked as an ibexa.cron.job and set to run every 5 minutes.

TODO:

• If action is to trash, remove schedules from the trashed content to avoid unexpected behavior when restored?
• Instead of marking schedules as evaluated and leaving the history, delete the schedule?

License

License