CUNY Academic Commons

I've copied the library. I already have a utility for doing this, which I've attached here in case anyone else ever needs it.

I'll do some tests later to see whether library files are being properly copied during the clone process.

Looks great. Thanks so much!!!

Actually, one note -- the three files listed at the bottom of the library (see screenshot) are, I believe, forum attachments. I wanted to delete them, so I clicked "edit," but that brought me to the posts in their original groups. Is there any way you can manually delete them for me? And maybe this is something to address in the cloning process?

Just noting, too, that I didn't see an attachment to your post. Is this utility something a dev would need to run from the command line or something that is user-facing?

It's something that has to be run from the command line. I've now attached the file (I hope).

Actually, one note -- the three files listed at the bottom of the library (see screenshot) are, I believe, forum attachments. I wanted to delete them, so I clicked "edit," but that brought me to the posts in their original groups. Is there any way you can manually delete them for me? And maybe this is something to address in the cloning process?

I'll open a separate ticket to address this.

==

I've done some initial analysis, and it looks like we have a problem with Cavalcade. When cloning, library copying is handled as a scheduled task. See http://github.com/cuny-academic-commons/cac/commit/8eade9f3c2220be7f48a880203fa54af0849978d. It appears that these events are not being fired. In fact, it appears that no scheduled events are being run at all - when I look at the queued items in the cavalcade_jobs table, Based on a cursory look at a few sites, it looks like jobs have been queuing up since sometime on August 27 or 28.

Ray, you have done some debugging work on Cavalcade in the past. Can you confirm my hypothesis?

It could be that the daemon is down. I believe Lihua had it set up as a systemd process. To fix, we'd need to find someone at the GC who knows how to log into the proper place to diagnose. It could be as easy as restarting the process. But I don't know who this person would be.

If we can't fix Cavalcade because of issues at GC IT, then we need to find some other solution for scheduled tasks. Maybe back to WP's pseudo-cron. Or I could imagine writing a bootstrap for Cavalcade that runs as an actual job on the crontab.

Actually, one note -- the three files listed at the bottom of the library (see screenshot) are, I believe, forum attachments. I wanted to delete them, so I clicked "edit," but that brought me to the posts in their original groups. Is there any way you can manually delete them for me? And maybe this is something to address in the cloning process?

Matt, I've created #16690 for the general problem here.

However, in this case, there are four items with type 'forum_attachment'. See screenshot. Can you confirm that you want them all removed from the group?

I'm going to ship the solution linked in https://redmine.gc.cuny.edu/issues/9930#note-10 as part of today's release.