Caleb Burks

I'd like to, yes :). One day...

> by adding the post meta key _restrict_attachment with a value of true or 1 to an attachment. > in_array( $attachment_restrict_file_meta, [true, 'true', 'yes', 1, '1'] Since this is a...

Maybe needs adjustments post-https://github.com/Automattic/vip-go-mu-plugins/pull/1999. Of note, there's a good possibility of this module being deprecated and moved away from.

Confirming that we will be deprecating/removing the async publish posts module very soon. Going to leave this PR open for a little in case I'll be migrating the plugin to...

I'd still like to look into this and finish the PoC I started that'll allow us to trigger the activation hook one time for plugins activated via code. Is still...

An additional problem worth noting / solving: ## 4) The same exact event can be run multiple times concurrently. At the moment we complete/reschedule an event right before running it....

Did a lot of testing and thinking about all the above. And I think we can solve pretty much all of the problems by setting events to the `running` status...

> Specifically, we want to use this to clean out all one-time events when syncing a database between a production and pre-production environment on VIP Go. This is a good...

Solutions: 1) Sanity check in `list-due-batch`, perhaps if there is a relatively old event at the top it should scan the batch and resolve entries that have mismatches. 2) `list-due-batch`...

Leaning towards just giving the runner an event ID to run: `cron-control orchestrate runner-only run 123` it doesn't need all the other info. And w/ an ID, we can always...