Project

General

Profile

Support #14440

Cloning Media Library for JITP from Staging to Production Site

Added by Patrick DeDauw 5 months ago. Updated 4 months ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
WordPress - Media
Target version:
Start date:
2021-05-10
Due date:
% Done:

0%

Estimated time:

Description

Hi Boone,

Hope you're doing well and looking forward to the summer as much as I am.

The JITP is once again ready for a clone of its media library for April and May 2021 from the jitpstaging.commons site to the jitp.commons production site. Thanks so much in advance, once more, for your help on this!

The most recent ticket of this kind is #13663, the preceding one is #12824, and ticket #12177 has a set of reference notes.

Please let me know if I can provide any further information.

Thanks so much for your help,

Patrick DeDauw
Managing Editor, The Journal of Interactive Technology and Pedagogy

History

#1 Updated by Boone Gorges 5 months ago

  • Status changed from New to Resolved

Hi Patrick,

Good to hear from you, and thanks as usual for the detailed ticket references.

I've performed the sync. All files from the staging site should now be cloned to the production site. Let me know if you spot any problems, and happy spring!

#2 Updated by Patrick DeDauw 4 months ago

Hi Boone,

Thanks so much for the rapid turnaround. I now seem to be having the problem where new (as in added today) additions to the jitp.commons media library (we re-add our posts' Featured Images) are not showing up. I tested by just embedding the new additions to the body of a draft post (like this one: https://jitp.commons.gc.cuny.edu/wp-content/blogs.dir/614/files/2021/05/Featured-Image-6.png ) and came up with a broken image.

I know it's normal to not have the cloned media appear in the library, but this seems exceptional. Any ideas what's going on?

Take care,

Patrick

#3 Updated by Boone Gorges 4 months ago

Hi Patrick - Thanks for your patience as I sorted this out. I had mistakenly synced the entire directory from jitpstaging to jitp, which included an .htaccess file that we use for access-protection on the Commons. That .htaccess file contained a redirect rule that pointed requests of the form wp-content/blogs.dir/ to jitpstaging.commons. I've corrected the file and the redirects are no longer taking place in this way.

Note that you may need to flush your browser cache in order to see the changes, because the incorrect 301 redirects will be cached somewhat aggressively by your browser.

Ray, I'm CCing you just as a warning in case this happens in the future - beware of wholesale rsyncs!

#4 Updated by Patrick DeDauw 4 months ago

All good! Thank you so much. We seem to be set.

Have a great rest of your week.

Also available in: Atom PDF