stenberg.me

Thanks @phillyj8.

This could probably be handled by the plugin somehow, I’ll have a look at it.

Thanks for reporting this!

Authors of the posts that you deploy will automatically be included in the batch. Sounds like your user has been replaced, you are still able to login, but you do not have permission to do anything.

Thinking about it, we do not sync wp_user_roles (from wp_options), might be related.

In this dummy environment, do you have more then one user? Any plugin or code that might modify user roles?

Thanks!

Thanks, contributions are gladly accepted ??

I’m preparing a new release of the plugin on www.ads-software.com, the latest code is on GitHub. Master should be stable, pushed some code to it recently.

Could you take a look in the log and see if anything shows up during pre-flight?

Thanks!

Hi,

Great to hear that you like the plugin!

Yes, this is a bit tricky, what you will have to do is to add something like this to your code:

/**
 * Change endpoint if we are on something else then the master site.
 *
 * @param string $endpoint
 * @return string
 */
function my_new_endpoint( $endpoint ) {
	$site = get_blog_details();
	return $endpoint . $site->path;
}

add_filter( 'sme_endpoint', 'my_new_endpoint' );

Thanks for reporting this issue, I will try to handle this automatically in upcoming versions of the plugin so there is no need for adding custom code.

Hope this solves it!

Hi,

Thank you for using the plugin.

1. Was the post published on your content stage before deploying to production?

2. Yes, this should be possible and it actually works by default. We have not tested this thoroughly so I cannot guarantee that unexpected side effects won’t occur. If you discover any issues when testing this, please let us know ??

Thank you!

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?

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

WordPress Content Staging version 1.2.2

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.

Hi!

Two new hooks has been added in the last release of the WordPress Content Staging plugin version 1.2.1 that addresses this feature request.

The hook you want to use is called sme_imported and runs on the production environment after the entire batch has been imported:

function call_url_fix( $job ) {
	// Do something here ...
}

// Triggered on production when import is completed.
add_action( 'sme_imported', 'call_url_fix' );

If you would like to perform some operations on the staging environment as well after deploy is completed, you can use the sme_deployed hook:

add_action( 'sme_deployed', function() {
	// Do something on staging environment ...
});

Hope this helps!

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!

Hi Bruce,

It is now possible to keep batches even after they have been deployed. Just add the following to your code (e.g. to functions.php):

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

A new view has also been created that shows historic batches deployed to production. This History view can be found as a submenu item to Content Staging.

I really hope you will enjoy Content Staging version 1.2.1

Glad to hear that the plugin is of help!

Currently there is no sme_deployed hook, but as you correctly points out, there really should be!

I’ll make sure to include this in the next release, I will keep you posted on any progress on this.

I’ve created an issue to address this: https://github.com/stenberg/content-staging/issues/56

Thanks for the feedback, really helpful!

We have released a new version that addresses the category sync issue and also includes some other improvements we’ve been working on.

I will keep you posted on any further progress on the other issues that you’ve pointed out.

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.