nfreed

Actually, I don’t know if it’s a timeout issue, because the corrupted filename is showing up in the modal download dialog *before* the file actually starts downloading. I don’t even think my server is reaching the actual file—rather something like the (html or php or whatever) download page.

They’re pretty small files, actually—from a few hundred K to a few megabytes. Not anything modern technology should have any trouble handling.

I’ll check with my web host about the timing out. Do you know if there’s a way to measure that?

So then, how does it work to clone the staging site back to the original site, if the original site uses security plugins that modify directory and database names and redirect based on these? Won’t these be overwritten when the staging site is cloned back to the original, thus breaking the site?

Thanks, Rene. The URL shows as the original site URL, even though I had to re-login. So clearly it’s not the staging site.

So then I can’t create a staging site that’s an exact mirror of the original site, with security plug-ins? That’ll essentially be useless to me, because when I copy the staging site back to the original (which *does* have the security plug-ins and redirects), all the links and redirects will be broken. That doesn’t make a lot of sense, unless I’m missing something here.

Shirley, it may be a theme compatibility issue with the latest version of WordPress. I was able to resolve mine by updating my theme (Divi by Elegant Themes) to the latest version. Check with your theme designer to see if this is a known issue and if there’s a fix available.

I’m having a problem with disappearing images under 4.5.x also, Shirley. The only thing that worked to fix it was restoring a previous 4.4.2 install. It’s clearly a WordPress 4.5 compatibility issue. I’ve disabled automatic upgrades until this issue can be fixed.

This does not appear to have been fixed in WordPress 4.5.2.

It seems as if the “Review Order” page is an artifact of the WooCommerce PayPal plugin, which got temporarily enabled, then disabled by the support rep. I’ve referenced a thread from this forum above that references it.

As for the SSL, I have a security certificate and WordPress is installed on https, but I don’t know enough about the technology to know what’s required beyond that. The WooCommerce docs seem to indicate that forcing the entire site, and not just the checkout pages, to run over SSL would result in slowdowns. So I chose the option to just enable the checkout pages.

But that’s not really the point. The point is that everything was functioning fine with the Force SSL on the checkout pages before the support rep broke it. I want to go back to that. There should be a simple way to figure this out.