When I click Pre-Flight Batch, I get this error:
transport error: http_request_failed A valid URL was not provided. – on host: (error code -32300)
Where am I supposed to specify the ‘Valid’ URL? Is it under settings, Remote URL? I have tried specifying both the Staging and Production URLs. I keep getting this same error.
Also, getting to this point has been a trial and error process as there is a general lack of documentation.
Please help, as I can see that this would be a very useful tool.
Thanks,
-Gary
Hello,
I tried to push a post to production and received this error:
Fatal error: Call to undefined function Me\Stenberg\Content\Staging\XMLRPC\gzcompress() in /var/www/production/wp-content/plugins/content-staging/classes/xmlrpc/class-client.php on line 388
Any thought on how it could be fixed?
Thanks!
]]>is it necessary for the receiving (i.e. Prod) Remote URL setting to be pointing back to your downstream (i.e. Stage) environment and then changed if wanting push through a three environment setup? or can the Remote URL in a QA environment be set to Prod while Remote URL in Stage is set to QA?
]]>Hi, Love your plugin, but I am having one issue. URLs in link and to media, etc are retaining the staging site url in the prod environment. I had to make some direct db edits for other reasons, so I am assuming that I accidentally changed a setting that I shouldn’t have. Can you point me in the direction of where that would be stored?
]]>get transport error: http_request_failed couldn’t connect to host – on host: (error code -32300) when attempting to deploy batch
what ports need to be open in firewall to allow /xmlrpc.php file to be accessible?
]]>Noticing in custom post types you can’t just deploy straight to production as you can in pages and posts.
Also is there a way to clear a history of changes the page is just getting so long after so many.
]]>Is anyone else having a problem with cats/taxes not being applied on the production side after a push?
Everything else is working fine, just losing its association in production.
Noticed in 4.4 and 4.4.1
]]>I see some chatter about Images/Attachments, so I’m just curious if there is a hook to grab all media attached to a post that has custom fields and those fields contain images. Or is this just part of the bug that looks like is trying to be solved for?
]]>The Production environment need access to the attachments directory (usually wordpress/wp-content/uploads) on the Content Staging environment.
File access or http?
Do attachments get copied to the production server?
Post has a parent post that does not exist on production and is not part of this batch. Include post About in this batch to resolve this issue.
I don’t know what to do. I’ve included the post i’m trying to push, and its parent and still get this error. I made sure the guid in the db matched up too.
]]>This looks like a great plugin. Does it fully support WPML?
]]>I can’t seem to install the plugin, I de-activated all other plugins. This is a fresh install from your github.
Plugin could not be activated because it triggered a fatal error.
Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /wp-content/plugins/content-staging-master/content-staging.php on line 81
]]>I am assuming you can’t delete pages or posts with this? For instance if you don’t need the post anymore and delete it, that doesn’t get synced with the live site then.
]]>When trying to send data from staging to production my preflight returns a success message but when trying to import the data the process never finishes. I’m not getting any errors or a time out. Any suggestions?
]]>Hello I’m running into this error
parse error. not well formed – on host: productionserver.com (error code -32700)
when I enter preflight from my staging server and I’m not sure how to get around it. I’ve seen forums mentioning that there could be whitespace in the xmlrpc file but that file is in stock condition.
Any help would be appreciated. Thanks.
Maybe just a multisite issue, could not try it in another machine.
I have tried to transfer a linked image from the library from one subsite (Multisite setup) to another by deploying the post.
The image was shown with the source domain url.
I was expecting that the image would be added in the target’s site database and a copy placed in the uploads (I agree that the uploads can be the same folder but each site should have their own uploads: /uplods/2/2015… “2” being one site ID)
After installing WP Document Revisions plugin, I tried with this new Document post type and it transferred the database entry, but the link is broken in the media edit page
/documents/2015/06/regen (extension “png” missing)
Hard for me to tell, where the crack happens.
I will see if I can setup a single instance environment
thanks
]]>Is it feasible, that Selected media could be staged as well?
Textual content is one thing, but a set of [updated] images need to be staged as well and this does not seem to be offered.
Will content and their inline media references update media as well?
I have a lot of other ideas but need to gather them and think if I extend this plugin eventually.
thanks for this plugin. Hope we have a use for it if our Intranet goes WordPress.
]]>I get the following error message when trying to active the plug-in:
Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home/nesfirst/public_html/CHSDev/wp-content/plugins/content-staging/content-staging.php on line 79
]]>Getting this after clicking pre-flight.
]]>So does this plugin not carry over the images at all? I just uploaded a feature image and saw that it did not carry over at all to the live. I guess you have to re-add and reupload all the images? Does this hold true if a person uploads an image in their content?
]]>I have just installed this plugin in my local dev environment. However, I do not see settings menu when I click on content Staging. Am I missing something?
In the installation instruction, you said that I need to add this in my staging environment
define( ‘CONTENT_STAGING_ENDPOINT’, ‘https://_YOUR_PRODUCTION_SITE_.com’ );
My question is why is the endpoint is the url of my production site?
thanks,
]]>As mentioned in the other thread, the last time I deployed a test batch, I ran it with only 1 page, which already existed on the target site. Instead of updating the page, it duplicated it. Any idea why?
]]>Hello,
This time, I created a new setup. A ‘production’ site, and a ‘staging’ site cloned from ‘production’. Exact same site, save for URL.
Installed Content Staging and configured wp-config on both sites. However, when trying to pre-flight, I got the following error message:
transport error – HTTP status code was not 200 (403) – on host: https://[siteURLhere] (error code -32301)
I double checked secret key (a SALT key) and it was a match. Changed to a simpler one, still not working.
There seems to be a similar error code with Jetpack plugin reported at:
https://www.ads-software.com/support/topic/what-is-error-code-32301
If it’s host specific, my new setup is hosted at Cloudways.com
Any clue?
Thanks!
Bowo
It’s not obvious from the plugin description and FAQ page, but it seems that the plugin only deploys new posts?… Will it deploy edits/changes to existing posts?… If not, why not?
Still trying to find a solution to enabling edits on staging to be deployable to both production and also dev environment.
A related question: assuming that deploying edits to existing posts becomes possible, is the way the plugin works overwrites the entire _posts and _postmeta tables?… Or, does it only sync differences/changes?
I’m asking because to my understanding, syncing data/content between environments is still very much a tricky business. Something that the likes of https://versionpress.net and https://revisr.io is trying to solve, and Migrate DB Pro is doing very well, save for the fact that the migration overwrites the destination DB table (AFAIK).
So maybe, if this plugins handle ‘posts’ syncing very well, it could be something potentially useful to many?
Thanks!
Bowo
Just did a test. One new post and one new page were deployed successfully on production. However, after deployment, I was logged out on production. Logging in gives me “You do not have sufficient permissions to access this page.” error, so can’t view any of the wp-admin pages.
Interestingly, new post and new page shows the admin bar on top saying I’m logged-in, but going to the dashboard or my profile editing page gives the same error. Not sure if this is caused by something on my production site, or by this plugin and/or a bug in the deployment process.
FYI, this is a dummy DEV/TEST/LIVE environments, and I’m deploying content batch from a 4th environment, let’s call it CONTENT. So, no actual harm was done other than me not being able to access my dummy production environment.
]]>Glad to have found this precious gem. ??
I’m currently testing and would like to know if it’s possible to set it up in a way that it pushes to both LIVE and DEV environments at the same time.
The reason I’m asking is this specific, yet potentially, generic need:
1. I have DEV, TEST and LIVE environments set up. The way the site is developed requires me to push content (DB _posts and DB _postmeta tables) from DEV to TEST to LIVE from time to time using Migrate DB Pro.
2. With Content Staging plugin, site owner (my client) would be able to push from a CONTENT environment to LIVE.
3. However, when I need to push content from DEV to TEST to LIVE, it will overwrite content deployed in step 2 above.
4. Thus, ideally, being able to push from CONTENT to both LIVE and DEV will solve the above issue?
Thanks!
Bowo
I’m trying to use this plugin (which is great, by the way) in a multi-site environment. When pushing from development to production, all of the posts went to the root site in the multi-site environment, rather than the destination site.
Did I set it up wrong?
]]>Hello,
Great plugin. Just have two issues:
1. When we push content from staging to live, the status of posts become Draft instead of published.
2. Also, is it possible to be bi-directional. In other words, can we setup the plugin to allow push from LIVE to STAGE and STAGE to LIVE as well?
Thanks.
]]>Hi!
First off I’d like to thank you for this plugin! Really helpful ??
I’d like to call a php file on my production server that does some DB cleanup after the batch has been sent. I tried adding the code below to my functions.php without any luck, am I using the hook correctly?
add_action( 'sme_deployed' , 'call_url_fix' );
function call_url_fix() {
file_get_contents('https://domain.com/db-cleanup.php');
}Thanks!
]]>To the developers:
This is an excellent plugin and I would like to eventually donate to the plugin, but I need to see some improvements of how this would work:
1. Batches on staging should not disappear after deployment
2. Ability to assign users rights to deploy certain content
3. Categories between staging and production are not perfectly synced.
I see on GitHub that it can be extended, but there is no explanation of how to use each hook.
Please see the reviews page for more details on the functionality that I am looking for.
]]>