CUNY Academic Commons

Yes, most likely this is due to the new bbPress hardening changes.

The crosspost feature works by setting up a cronjob to post the topics later. It's most likely that since the cronjob does not use the authenticated user, that the topics are failing to post due to the new hardening changes. Will see how we can work around this.

I tested locally and the multiple forum post functionality is working, so I checked production and the cronjob to duplicate the forum post hasn't run yet because there is a cronjob lag on production of about six days.

I'm working on clearing the log.

Boone, can you tell if Cavalcade is running on production? Because it doesn't look like the queue is going down at all.

According to the Cavalcade database, the next job to run is 2026-09-22 21:47:09, which is six days ago.

Hm. It appears to be running. Here's a couple checks, about 5 seconds between:

litespeed@node15377-cunyacprod-1 ~ $ ps aux | grep caval
litespe+ 1033877  0.4  0.0 261000 39828 ?        SNs  21:08   0:00 php /usr/local/bin/cavalcade
litespe+ 1048520 81.5  0.1 287812 128816 ?       RN   21:10   0:01 php /usr/local/bin/wp cavalcade run 6758431 --url=abifacultyseminarseriessummer23.commons.gc.cuny.edu/
litespe+ 1048707 53.0  0.0 274204 64376 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6740803 --url=senses.commons.gc.cuny.edu/
litespe+ 1048708 42.0  0.0 269948 52372 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6094975 --url=zainabkhan73.commons.gc.cuny.edu/
litespe+ 1048709 31.0  0.0 269948 52216 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6075797 --url=ktg2004.commons.gc.cuny.edu/
litespe+ 1048720  0.0  0.0   7068  2040 pts/2    S+   21:10   0:00 grep --color=auto caval
litespeed@node15377-cunyacprod-1 ~ $ ps aux | grep caval
litespe+ 1033877  0.4  0.0 261000 39828 ?        SNs  21:08   0:00 php /usr/local/bin/cavalcade
litespe+ 1049272  177  0.1 287808 118356 ?       RN   21:10   0:01 php /usr/local/bin/wp cavalcade run 6748173 --url=bmccmusic.commons.gc.cuny.edu/
litespe+ 1049532  0.0  0.1 276636 80056 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6744037 --url=transformation.commons.gc.cuny.edu/
litespe+ 1049534  0.0  0.1 274588 72264 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6750919 --url=help.commons.gc.cuny.edu/
litespe+ 1049535  0.0  0.0 274204 66028 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6641181 --url=brownf26110.commons.gc.cuny.edu/
litespe+ 1049648  0.0  0.0   7068  2052 pts/2    S+   21:10   0:00 grep --color=auto caval
litespeed@node15377-cunyacprod-1 ~ $ ps aux | grep caval
litespe+ 1033877  0.4  0.0 261000 39828 ?        SNs  21:08   0:00 php /usr/local/bin/cavalcade
litespe+ 1050245  105  0.2 380932 196172 ?       SN   21:10   0:03 php /usr/local/bin/wp cavalcade run 6742525 --url=newtestsite.commons.gc.cuny.edu/
litespe+ 1050497  108  0.2 298220 159656 ?       RN   21:10   0:02 php /usr/local/bin/wp cavalcade run 6739689 --url=help.commons.gc.cuny.edu/
litespe+ 1050507 96.0  0.2 368804 152712 ?       RN   21:10   0:01 php /usr/local/bin/wp cavalcade run 6742435 --url=acertdev2.commons.gc.cuny.edu/
litespe+ 1050538 94.0  0.2 373588 148344 ?       RN   21:10   0:01 php /usr/local/bin/wp cavalcade run 6739827 --url=tokyo2021.commons.gc.cuny.edu/
litespe+ 1050686 88.0  0.1 278684 85172 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 6742821 --url=ccnypsaproject.commons.gc.cuny.edu/
litespe+ 1050721  0.0  0.1 276636 76700 ?        RN   21:10   0:00 php /usr/local/bin/wp cavalcade run 4304253 --url=ausher.commons.gc.cuny.edu/
litespe+ 1050869  0.0  0.0   7068  2052 pts/2    S+   21:10   0:00 grep --color=auto caval

So you can see that the daemon is indeed working through the queue, though I can't say from this alone whether it's enough to catch up.

Thanks for confirming, Laurie. Can you also check the site cloning issue to see if that is resolved as well?

The cronjob queue is now clear.

Boone, I made a change to Editoria11y on production to change their cron job's batch size from 1000 to 100: https://github.com/cuny-academic-commons/cac/blob/f892c9950d621354f4c940357a4e4488b070233c/wp-content/plugins/editoria11y-accessibility-checker/src/Installer.php#L75. I also made a change so their cronjob only runs every 30 mins instead of every 5 mins. Both of these changes haven't been committed yet.

I've also posted an issue on Editoria11y's Github repo about their cronjob, aided by an AI audit: https://github.com/itmaybejj/editoria11y-wp/issues/61.

Let's keep an eye on Cavalcade and see if there any more lockups over the next day or so.

Update: Dropping the batch size didn't help as I noticed a 2-hr hanging task a couple of hours after the queue was cleared. I've since killed that task.

Thanks to you both for looking into this.

I think we already have done this but Editorially could be removed as one of the plugin that comes pre-installed on every site during site creation (since it sounds like it may be part of the issue)