ServerPress
Forum Replies Created
-
Forum: Plugins
In reply to: [WPSiteSync for Content] when the plugin can sync to multisite?Hi zfbd,
Thank you for your interest in WPSiteSync.
We do support MultiSite. You can set up any WordPress install as a Target for synchronization with WPSiteSync.
Let us know if we can help you with anything else.
All the best,
The ServerPress TeamForum: Reviews
In reply to: [Database Collation Fix] Worked for version 5.5.3Hello Azamat,
Thanks for the feedback! It’s been a while since we’ve updated this so we’re happy to hear that it’s working well.
And very happy to hear that it solved your problems.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] Same Title/Slug, Different Level (parent)Hello, janavar23.
We’ve responded to the other ticket you created here: https://wordpress.org/support/topic/pages-being-overwritten-even-after-changing-the-title-and-slug/
You’re seeing a slightly different issue but we’ve provided instructions on how to get you fixed up in that support issue.
All the best,
The ServerPress TeamHello janavar23,
Thank you for your interest in WPSiteSync.
This is not a cache issue. When we synchronize content, we store in the database the Source site and Target site post IDs. This way, subsequent Push operations will re-use the same post IDs. If you’ve changed the post title and/or slug, it’s still the same post ID so it will continue.
To clear this, you can remove the entry in the wp_spectrom_sync table where the target_content_id column matches the post ID on the Target site. You will have to do this on both the Source and Target sites.
As an alternative, if you don’t want to work in the database, you can change the WPSiteSync configuration and set the “Optionally remove Settings and Tables on plugin uninstall” to “Yes, remove all settings and data on uninstall.” Then, deactivate the plugin, delete the plugin, and then re-install the plugin. Again, you will need to do this on both the Source and Target sites. This will clear the database tables, removing the post ID associations.
If this does not resolve your issue, feel free to contact our support team at https://serverpress.com/contact/ and submit a ticket there.
We are working on a fix for the issue that causes this, the “same slug, but different parents” issue you referenced. We will be releasing this with our next update but we do not have an expected date for this yet. We will update this issue here in the support forums when we do release it. And if you contact us we can let you know via email.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] Same Title/Slug, Different Level (parent)Hi monkeyleo13,
Did you also submit this to our support page at https://serverpress.com/contact/ ?
I ask because we had another support issue this week that looks similar to this. If you did not, please submit a support ticket at the URL above and let us know you are monkeyleo13. We would like to get some log files from you so we can work on this.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [Rank Math SEO – AI SEO Tools to Dominate SEO Rankings] dateModifiedHello seanpaulfx,
I thought I’d jump in here as the developer of WPSiteSync and make a comment.
The datePublished value is stored in the post_date column in wp_posts. The dateModified is stored in the post_modified column. Your sample code is not providing a new value for post_modified, so wp_update_post() uses the old value from the database.
I looked at the code for wp_update_post() and I think you can add two more arguments like:
‘post_modified’ => ‘0000-00-00 00:00:00’,
‘post_modified_gmt’ => ‘0000-00-00 00:00:00’
and it should clear the modified dates, making the post appear to be new.I hope that helps you.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] WordPress 5.5 issueHi whanklee,
Alright, that message does look different. And the 404 error is not what we were seeing before.
We’re working on reproducing this ourselves so we can look a bit deeper. We’ll let you know when we have something. In the mean time, if you would contact us via our support page we can work with you more efficiently: https://serverpress.com/contact/ Be sure to tell us your WP username.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] WordPress 5.5 issueHi whanklee,
Sorry to hear that you’re still having problems.
Let’s make sure we’re looking in the right place. While on your Source site, can you open up the “Inspector” tool in your browser and go the the “Console” tab? This is the Javascript console. When you click on the “Push to Target” button, you’re probably seeing a big, ugly, red error message in the console. Please copy and paste this message into your next reply.
It’s probably mentioning a error in sync.js line 460. If that’s the case, the Javascript files may be cached by your browser. You need the new versions of these files. Try refreshing the page by holding down the Shift key and pressing F5 or clicking on the Reload button, also while still holding down the Shift key. This will force new copies of JS and CSS files to be downloaded. Then try again and see if it still doesn’t work. If it’s still not working we can use the copy/paste of the error message from the Javascript Console to diagnose the problem and get you a fix.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] What needs to be enabled for this plugin to workHi ilovecake,
Thank you for your interest in WPSiteSync. This is a great question.
The WPSiteSync plugin does not use XML-RPC or the REST API to perform it’s API operations. It also does not rely on the /wp-admin URL for any of it’s operations. The security measures you describe don’t sound like anything that would affect the performance of our APIs. We also take into account the current URL structure needed for image references, so if you are not using the same WP path structure on the Source and Target, the paths will be adjusted so that the content and images work correctly once everything arrives on the Target site.
All that said, there may still be other plugins and non-standard configurations in your install. While we’ve taken all the steps we can think of to ensure everything works in all environments, the only way to know is to test. If you do find any problems we would appreciate the opportunity to work with you and resolve any issues you may come across.
And we love cake too. 🙂
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] WordPress 5.5 issueHello whanklee,
There is a small Javascript problem that we noticed with one of the more recent releases of Gutenberg last month and those changes are also in the latest WP 5.5 release. We have an interim fix that you can download here: https://www.dropbox.com/s/fykiu23y0j3v30z/wpsitesynccontent.1.6.1b.zip?dl=1 if you don’t want to wait for our next release in the WP repo. The next release is coming soon, but we can’t give an exact date just yet.
If you do notice any issues with the interim release, please let us know via our contact form at https://serverpress.com/contact/
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] ACF Pro SupportHi Jason,
Thanks for asking about WPSiteSync for ACF Pro. We do not have a release date but we are working on it.
If you’d like contact us at https://wpsitesync.com/contact/ and let us know you’d like to subscribe to our newsletter we can let you know when it’s available.
All the best,
The ServerPress TeamHi Francis,
Thank you for your interest in WPSiteSync.
Currently, WPSiteSync only Pushes from one Source site to one Target site. We are developing an add-on that will allow Pushing to multiple Target sites, but we do not have a date for that release.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] can we use this for site repicationHello psrinivas,
Thank you for your interest in WPSiteSync.
WPSiteSync allows a user to synchronize individual pieces of content- pages, posts, etc. We do have a “Bulk Actions” add-on that allows you to synchronize multiple pieces of content, but this is still done on demand, with a user driving the activity in the Admin. WPSiteSync is designed to be used to synchronize the content as needed. Not automatically or all content at once.
I think you’re better off using a database migration tool. There are several available that you could probably automate much easier than doing the same thing with WPSiteSync and they work in the MultiSite environment.
Once the content is migrated to a new site, new content can be synchronized with WPSiteSync. But again, that would be done on demand and not automated.
There is also WP Ultimo, which allows you to create a site on the network that acts like a “template”. When new sites are created, this template can be copied to the new site. That might be worth looking at.
Best of luck on your project.
All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] Change target post timeHello divixmu,
For some reason our support form didn’t forward the email to our support ticket system. We’ve found your support request and are replying to that email.
The code you’re showing above would reset the post_date to the current date/time, each time you Push the content. And it sounds like that’s what you are describing.
For others that may be interested, the following code will modify the post_date, adding for example, two hours.
add_action( ‘spectrom_sync_push_content’, ‘sync_update_post_date’, 10, 3 );
function sync_update_post_date( $target_post_id, $post_data, $response )
{
$new_post_date = DateTime::createFromFormat( ‘Y-m-d H:i:s’, $post_data[‘post_date’] );
// adjust DateInterval as necessary to change the post date
$new_post_date->add( new DateInterval(‘PT2H’) ); // T=time H=hours- add two hours to post_date
wp_update_post( array(
‘ID’ => $target_post_id,
‘post_date’ => $new_post_date->format( ‘Y-m-d H:i:s’ )
));
}All the best,
The ServerPress TeamForum: Plugins
In reply to: [WPSiteSync for Content] Change target post timeHi divixmu,
I think I see the problem. Please submit a support request ticket to our Support team here: https://serverpress.com/contact/
We check this several times a day and can respond to you faster there. In the mean time, we’ll work on some changes to the code above.
All the best,
The ServerPress Team