Hi,

we did some testing on our installation, and if i run the update script:
php bin/console ngscheduledvisibility:update --no-interaction

we get the following warning which produces an error log item:

[2024-06-27T11:58:56.192903+00:00] console.CRITICAL: Error thrown while running command "ngscheduledvisibility:update". Message: "Warning: DOMDocument::loadXML(): xml:id : attribute value 146092 is not an NCName in Entity, line: 2" {"exception":"[object] (ErrorException(code: 0): Warning: DOMDocument::loadXML(): xml:id : attribute value 146092 is not an NCName in Entity, line: 2 at /mnt/data/htdocs/ib46-fide/vendor/ibexa/fieldtype-richtext/src/lib/FieldType/RichText/RichTextStorage.php:139)","command":"ngscheduledvisibility:update","message":"Warning: DOMDocument::loadXML(): xml:id : attribute value 146092 is not an NCName in Entity, line: 2"} []

It looks like an xml object is not valid. We imported some articles and converted the ezxml items with the ibexa utility.

....
1. we think a script which is updating the visibility status of an object should not break if something is wrong in an richtextfield

=> the script should be ignore the problem objects and process the other objects.

2. we don't know which object can not be processed => an extended log or view of the processing item would be good to have (maybe a verbose option which output the processing items with date publish_from => publish_to and id + name would be helfpfull

3. I don't know how the output looks like if it processed an item successfully and reveal it ... in that case a console output could be usefull too with contentid/locationId publish_from publish_to and name
   This output can than be piped in cronjob logfile
   Or we have an extra logfile for that. So that you can say when an article was made visible or unvisible by cronjob ...

How can the script

bin/console ngscheduledvisibility:update

be run as a cronjob?

The script asking to type yes to continue.

I think we need an option to force execution, so no useraction is required.

For big installation it could be a problem to process everytime all articles
in the script php bin/console ngscheduledvisibility:update

a good option could be to sort the objects by modified date and only process the last xxx items --process_last_items_limit ...