ServerPress
Forum Replies Created
-
Forum: Plugins
In reply to: [WPSiteSync for Content] numerous PHP errors on setupHi Peter,
Thanks for the clarification. And we’re glad to hear that the changes are working for you!
Yes — these fixes, plus a few other changes, will be included in our next release. That will be coming soon.
Forum: Plugins
In reply to: [WPSiteSync for Content] numerous PHP errors on setupHi Peter,
Thanks for contacting us and letting us know about the error messages you’re seeing. And thanks for submitting a support request on our web site. We’ve sent you an updated copy to test and verify that the error messages no longer appear and we’ll be updating the version in the WordPress repository with these changes shortly.
Please feel free to let us know if you have any further issues we can help you with.
Forum: Plugins
In reply to: [WPSiteSync for Content] Can this be automattic?Hi Mhsabbagh,
Thanks for your interest in WPSiteSync.
We have a plugin that is in beta right now that provides these features as an add-on to WPSiteSync for Content. If you would like to test with that, please contact us via our support page at https://serverpress.com/contact/ and we can send you a copy via email.
Forum: Plugins
In reply to: [WPSiteSync for Content] Images within post not being pushedMarking as resolved.
Forum: Plugins
In reply to: [WPSiteSync for Content] Site Sync not showing after updateHi Pewela,
Did you see WPSiteSync showing on the Product editor page before? WPSiteSync by itself only works with Posts and Pages, not products. To use it with Custom Post Types like products, you need to use the WPSiteSync for Custom Post Types add-on. It’s possible that the license for the WPSiteSync for Custom Post Types add-on has expired.
If you submit a request via our support page at https://serverpress.com/contact/ and give us your email address, we can look up your license key and check that out for you.
Thanks!
Forum: Plugins
In reply to: [WPSiteSync for Content] Image transfer not working with Elementor & S3 CDNHi Andreyk,
Thank you for your interest in WPSiteSync. Unfortunately, the Elementor plugin (as with other page builders like Beaver Builder, Divi, etc.) store some information in a way that is not recognizable by WPSiteSync by itself. These page builders require additional handling which is supported via add-on plugins for WPSiteSync. As such, we do not yet support Elementor.
WPSiteSync should work with CDNs, however. If you Push a page/post that is not built with Elementor, do the URLs work? If not, we would like to ask you to contact us via our support page at https://serverpress.com/contact/ where we can work with you better.
Thanks!
Hi Denis,
We’re sorry to hear that you’re having trouble.
If you only have one live site then I’m not sure that you need WPSiteSync since it’s used to move content between sites. But maybe I’m misunderstanding you.
The message “Unable to make API request to Target system.” usually means that there was a PHP runtime error on the Target site that is making the WPSiteSync tool unable to get an expected response from the Target. This can be caused by your theme, or a plugin or some other code conflict on the Target site.
Please submit a support ticket at https://serverpress.com/contact/ and provide us with your Target site URL. We’d be happy to help you out and find a solution.
Forum: Plugins
In reply to: [WPSiteSync for Content] Only one item at a time or bulk?Closing issue.
That error message means that there is something interfering with the WPSiteSync API on the Target site. This could be a “Coming Soon” or “Maintenance Mode” type plugin (or feature of your theme) that is blocking public access to the site, or it could be from a HTTP password required via an .htaccess rule, or possibly something like a security plugin.
Please check if you’re using a plugin like one of those that could be blocking access to the site. Disable any features like this that can cause problems and try again. If you’re still having trouble, please submit a support request via our web site at https://serverpress.com/contact/ and let us know the URL to your Target site and we can investigate further.
Forum: Plugins
In reply to: [WPSiteSync for Content] Please Update the plugin for Latest WordpresHi wordpress1209,
We’ve done some testing with WP 4.8.1 and WPSiteSync 1.3.1, pushing a post with a post format of ‘video’. The tests were successful. This tells me that it’s probably some conflict with another plugin or your theme.
If you could provide a copy of your site as mentioned above we could do some testing with it and see about coming up with a fix or a workaround.
Forum: Plugins
In reply to: [WPSiteSync for Content] Please Update the plugin for Latest WordpresHi wordpress1209,
We’re sorry to hear you’re having trouble with this. Thanks for bringing this to our attention. We will investigate this and come up with a fix for you.
It might be helpful to get a copy of your site that we can use for testing. Would you be open to that? Could you submit a support request at https://serverpress.com/contact/ – once you do this, you can submit an archive of your site via our HelpDesk tool.
Thanks again for letting us know.
Forum: Plugins
In reply to: [WPSiteSync for Content] Toolset CompatibilityHi Frank,
Yes, we’re familiar with ToolSet. WPSiteSync does synchronize all meta data associated with the Post being sync’d. So it should work with almost all data stored by ToolSet. Where you would run into trouble is if the metadata refers to other posts or to Images. This requires special processing in order to find the correct image, move it to your Target site and adjust the references (the different Post IDs) on the Target. This is the reason we’ve built special plugins to handle the data for Divi, BeaverBuilder and ACF: to handle these post/image references. So if your ToolSet metadata is not referring to any post IDs, it should work for you. Otherwise, it would require an add-on to fully support the data used by ToolSet.
We’ll add ToolSet to our roadmap and make sure that we handle the data correctly. Unfortunately, I cannot give you a date on when that would be ready.
Hi Frank,
Sorry that you’re having trouble with this. You are correct: the mcrypt library needs to be installed. I see that you did this via Homebrew, so you should have the files on your system now.
Two things for you to check:
1) Is the extension configured correctly? There are settings in php.ini which dictate where the directories are that store the mcrypt files. These may need to be adjusted depending on where Homebrew placed the files.2) You need to restart Apache and not MariaDB since these are extensions for the PHP install. After you’ve restarted Apache, you should be able to run a php –info (or call php_info() from within a .php file and load this in your browser). This will show all extensions that have been loaded by PHP and will include information on mcrypt when it is properly installed. Once you see this here, the error message will disappear.
Also note, that if you’re using a custom PHP install on your Target site, you may need to install mcrypt there as well.
Hope this helps and let us know if we can give further assistance.
Forum: Reviews
In reply to: [WPSiteSync for Content] Bugs!!Hi llb0536,
Checking in again to see if you could please take the time to submit a pull request at https://github.com/ServerPress/wpsitesync for your changes. We have reviewed your proposed changes but we’re having trouble verifying what the effects would be. So a pull request would give us a much clearer view of what you’re suggesting.
Specifically, the logic issue in lines 716..789 is not a bug but rather intentional. We only want to Push attachments that are part of the Source site (i.e. in the Media Library or somewhere else on the Source site’s domain) and not external references. This is because those external references will still be external references on the Target site. But local images do need to be Pushed, so this part of the code looks for those and sets them up to be sent along with the content.
We do, however, need to upload files (images or PDFs) to the Target site as these can be changed on the Source site. The Target site’s logic in handling these requests will replace the modified resource references to make all of the content on the Source match on the Target.
And the code on line 330 of apicontroller.php is already commented out so removing it has no real effect. The references to the Source site’s domain are correctly updated with the Target site’s domain in another area.
We don’t believe any of these are problems and we have not had any customers reporting issues in these areas. But we’d really appreciate the opportunty to work with you on these and clear up any problems if they do indeed exist.
Thanks for your interest and we hope to hear from you soon.
Forum: Reviews
In reply to: [WPSiteSync for Content] Really isn’t ready for productionHi Chris,
We’re sorry to hear that you’re not getting the support you are looking for. We checked our records and cannot find any issues submitted by you. However, we were having email issue on our server last summer when we launched. We tried to communicate this with our users but you may have fallen through the cracks and we apologize for that. We wish that you would have contacted us sooner rather than waiting for so long and being unhappy.
We have been trying to isolate the issues with the security plugins so that we can be more compatible. Unfortunately we have not been able to find a solution that would allow our API to work yet and still allow the security plugins to provide their features. But we are working on it.
We do have a beta release for a new version of the Pull add-on that allows pulling content from the Target that does not yet exist on the Source site. If you would like to test with this version, please contact us via our support page at https://serverpress.com/contact/ and we’d be happy to send you this new version for your review and feedback.
Again, we apologize for not responding to your support issues earlier. Had we received that, we would have certainly replied and provided assistance. Our wish now is that you allow us the chance to prove to you that our support does indeed exist and that we can help your resolve your issues.