Production Ready?

I have been testing this module on a client's production server. I will post content in staging mode, log out, and then test to see if the content is visible in production mode.

So far, every instance of the new content has been visible to an anonymous user. This is unacceptable for my client, who places an embargo on information before press releases get sent out. An information leak could have pretty serious consequences.

I am actively looking for other solutions because I don't trust the stager module to keep content confidential.

@modulist,

Hi,

Have you been able to find a solution for the problem with this module? I happen to have the exact same issue, however, it works works when the driver is mySQL but it breaks when the driver is sqlSrv. If you have any suggestion, I will appreciate it.

Thanks,

Varun

Actually, no.

However, we are looking at a different approach for having a client-friendly way of pushing content from a staging environment to production. We're looking into using a drush script triggered by an HTML form to do the job.

Here's the approach in broad strokes:

1. Client makes edits on staging site
2. Client navigates to an admin page on staging site
3. Client presses [publish to live site] button or link
4. Drush makes backup of production site
5. Drush syncs files directory from staging to production
6. Drush syncs database from staging to production
7. Drush clears all caches on production
8. Admin page refreshes with link to production site

Hello,

Thank you for posting. I've just taken over this module and I assure you I'll look into this issue by this weekend. Thanks for contributing.

Hello,

FYI, there are in fact a lot of alternatives out there. Take Deployment for an example. It supports pushing contents from one site to another. You might want to check this page: Comparison of staging and deployment modules. @modulist: Drush Deploy seems somewhat like what you're looking for.

Closing this issue.