Does a nice job, but needs a lot of work for professional environments

Thanks a lot for reporting this!

We will immediately have a look at the issue with categories not being perfectly synced (https://github.com/stenberg/content-staging/issues/55).

We’ll also see if we can come up with a solution for keeping batches after deploy (https://github.com/stenberg/content-staging/issues/54).

User management is something we would like to support, but it might be some time before we are there.

We have now released a new version that addresses the issue with categories not being perfectly synced.

The new version also includes some other goodies that we’ve been working on for a while.

Content staging version 1.2.1 has been released with support for listing all batches, even those that has already been deployed.

A History view over batches deployed to production in that past has also been added.

I really hope you will enjoy these new features and that they will be enough for a five star rating ??

Thanks!

Thanks, Stenberg. The plugin is looking good, but there is a new issue.

I updated the plugin, but now it copies existing posts and pages that are edited to the production site instead of replacing them. So now I end up with a two of the same post or page. Can this be fixed?

Bruce

Thanks!

Had some trouble replicating this, but my guess is that you create a dump of your production database, then you replace all occurrences of the production domain with the content staging domain?

IF that is the case then the comparison that checks if the post exist on production will fail (the comparison is using the GUID of a post that in WordPress includes the domain name).

We are working on a smarter way of comparing GUIDs. Will get a new version up today.

Thanks. I look forward to the new version. I updated to the latest version.

One thing is that the batches are still being deleted after deployment, so I had to comment the code inside the delete_batch() method under classes/db/class-batch-dao.php between lines 130-143.

Bruce

Hi Bruce,

A new version is now available that hopefully solves the issue you had with posts being duplicated.

It should also be possible to keep batches even after they have been deployed by adding the following to your code (e.g. to functions.php):

add_filter( 'sme_batch_list_statuses', function( $statuses ) {
	$statuses[] = 'draft';
	return $statuses;
});

WordPress Content Staging version 1.2.2

Stenberg, this is great. Your support is excellent. I just improved my review and rating.

Would it be possible to add the ability to allow certain users or user roles to be able to deploy specific post types like “post”, “page”, “job” etc before this Wednesday?

Bruce

Thanks Bruce,

Sorry, no. There are some other issues I need to address before having a look at the user roles. I’ll let you know when we have something.

I’m thinking that administrators will have the right to specify what users should have the right to send batches.

Administrators should also be able to set what users can deploy what post types.

Does that sound like what you would like to see in a content staging user management system?

Yes. That would be great functionality to have