stenberg.me

Fixed and merged to the master branch.

https://github.com/stenberg/content-staging

Thanks, that’s really helpful!

So the problem seems to be that the delete functionality relies on the class DOMDocument – part of the PHP DOM extension. Most likely you don’t have this extension in your PHP package, causing the fatal error.

I’ll get rid of the DOM extension dependency somehow. Created an issue for this:

https://github.com/stenberg/content-staging/issues/76

For now I’ve moved the delete functionality to its own branch.

Thanks, that’s certainly inspiring!

Hi,

Thanks for giving the plugin a try!

No attempts to support the WPML plugin has been made yet. I believe WPML creates some custom tables in the database, if that’s the case it’s unlikely that the Content Staging plugin supports WPML out of the box.

The ambition is to support popular plugins, when that will happen for WPML is unclear.

Does this happen with any batch that you try to deploy? Can you have a look at the debug.log and see if there is any clues in there?

I’ve added support for deleting posts, will be included in next plugin release. If you want to try it out immediately, see https://github.com/stenberg/content-staging

Thanks!

Actually built an extension doing just that, will see if I can integrate it with the main plugin.

Hi,

These are the messages that you see?

Prepare import on xyz
Importing…

Take a look at the debug.log, anything shows up there during deploy?

What message(s) do you get during pre-flight?

Thanks for reporting back on this!

Hi Shonu,

Not possible at the moment, but absolutely something we will look at going forward, created an issue for this https://github.com/stenberg/content-staging/issues/72.

Inline media is not supported, but in scope https://github.com/stenberg/content-staging/issues/7.

Featured images are currently working.

Alright, are you sending content from your production environment to your content stage?

Normally it’s the other way around, but whatever works for you is fine.

What you probably have to do is to include an Authorization header when making a request to the environment protected by Basic Auth.

Here is an example of doing that, add it to e.g. functions.php:

function set_content_staging_client_headers( $headers ) {

	if ( defined( 'CONTENT_STAGING_BASIC_AUTH_USER' ) && defined( 'CONTENT_STAGING_BASIC_AUTH_PASSWORD' ) ) {
		$headers['Authorization'] = 'Basic ' . base64_encode( CONTENT_STAGING_BASIC_AUTH_USER . ':' . CONTENT_STAGING_BASIC_AUTH_PASSWORD );
	}

	return $headers;
}

add_filter( 'sme_client_headers', 'set_content_staging_client_headers' );

Then in your configuration file (wp-config.php) on the host that is NOT Basic Auth protected, add the constants:

define( 'CONTENT_STAGING_BASIC_AUTH_USER', '_YOUR_BA_USERNAME_HERE' );
define( 'CONTENT_STAGING_BASIC_AUTH_PASSWORD', '_YOUR_BA_PASSWORD_HERE' );

Probably something worth including in the plugin, but for now I hope this helps!

Hi Shonu,

Thanks for reporting this!

Transferring images linked to a post remains one of the key things to fix in the plugin, currently only featured images are correctly deployed.

Have a look at https://github.com/stenberg/content-staging/issues/7 for more information.

Thanks!

Hi Shonu,

Great suggestion, I’ve created an issue for this, https://github.com/stenberg/content-staging/issues/71

Hi,

Sounds like your target environment (production) is protected by e.g. basic auth. Is that the case?