Forum Replies Created

Viewing 15 replies - 136 through 150 (of 234 total)
  • Plugin Author ServerPress

    (@serverpress)

    Hello @fuentes990

    We would like to verify that you have PHP 4.0.2 or greater.

    Please add a file named phpinfo.php containing

    <?php

    phpinfo();

    To the Source and Target websites.

    Then visit in your browser and send us the result.

    The mcrypt_get_iv_size() function is built into PHP but may be disabled via your configuration.

    Plugin Author ServerPress

    (@serverpress)

    Hi danyellg,

    Thanks for writing to us and sorry to hear that you’re having trouble.

    That message could be caused by the use of WPML. I know that plugin creates multiple posts, one for each translated version of the main post.

    Would you be willing to send us a backup copy of your site so that we could take a look at it? You can use something like Backup Buddy, Updraft, or similar plugins to make a copy of the .php files and the database. You can send that to us via our support form at https://serverpress.com/contact/

    We’d be happy to take a look and see what the problem might be so you can try things out with the plugin.

    Plugin Author ServerPress

    (@serverpress)

    Hi Samjco,

    Thanks for writing to us. Yes, WPSiteSync is designed to allow multiple Source sites to Push Content to a single Target site. The first time you push any Content, it tries to find matching content (by post name) on the Target site. Once it does this, it saves an association of the Source’s ID and the ID of the Content on the Target. When you do this from another Source site, the same thing happens: it finds the matching content on the Target and saves the IDs. But it will save the unique post ID from each Source site separately, so subsequent Push requests will always find the same content’s ID on the Target.

    I hope that satisfies your question. Please let us know if you need anything more. If this does answer your question, we’d like to ask that you mark this issue as “resolved.” Thanks!

    Plugin Author ServerPress

    (@serverpress)

    Hello @hirantha,

    We’d like to ask you to send us an email at support@serverpress.com so we can monitor your issue. We will need access to your Target site in order to diagnose this further. Please include your WP, FTP and phpMyAdmin access details so we can troubleshoot. Thank you.

    Plugin Author ServerPress

    (@serverpress)

    Hello @hirantha,

    Thank you for contacting us.

    The “cannot write authentication token” usually happens when/if the database tables are not created correctly.
    Please try deactivating, deleting then reinstalling the plugin. If that still doesn’t work, verify that the database credentials have “create table” privileges.

    Please let us know if this solution works for you.

    Plugin Author ServerPress

    (@serverpress)

    Hello @shgotlib,

    Thank you for contacting us.

    In order to sync custom post types, you will need the WPSiteSync for Custom Post Types add-on.
    Please visit http://www.wpsitesync.com for more info.

    Plugin Author ServerPress

    (@serverpress)

    Hello Martin,

    Are you still having this issue? If so, any additional information would be helpful.
    Otherwise, if the issue has been fixed, we would appreciate if you could mark this thread as “Resolved”.

    Thank you very much!

    Plugin Author ServerPress

    (@serverpress)

    Hello @atodorov,

    Are you still having this issue? If so, any additional information would be helpful.
    Otherwise, if the issue has been fixed, we would appreciate if you could mark this thread as “Resolved”.

    Thank you very much!

    Plugin Author ServerPress

    (@serverpress)

    Hello Martin,

    Have you finished setting up WP Site Sync with all the fields filled out? The metabox will not appear if the settings are not complete. It needs to be authenticated on the settings page first. Or, if you’re trying to sync a custom post type and not using the CPT extension, that could be another reason why the metabox isn’t showing up.

    If the above conditions have been met and still, the metabox doesn’t show up. Please send us an email at support@serverpress.com so we can assist you further. Please provide the login credentials to your Source site so we can take a look.

    Hello Kalico,

    It appears you are running Jetpack and using their CDN. Locally you are behind a router/firewall which would block incoming requests.

    You can go into the wp-config.php file and add the JetPack developer define and this will allow your site to pull it’s images from your lical media library.

    You can turn on Development Mode by adding define( ‘JETPACK_DEV_DEBUG’, true); to your wp-config.php file. Make sure you add it before the /* That’s all, stop editing! Happy blogging. */ line.

    We hope you find this information helpful.

    Plugin Author ServerPress

    (@serverpress)

    Great! Glad to hear you got it working. Please let us know if you need anything else.

    If this issue is resolved, would you please mark it as “resolved?” We’d appreciate it.

    Thanks and have a great day.

    Plugin Author ServerPress

    (@serverpress)

    Okay, the “Call to undefined function mcrypt_get_iv_size()” is the clue. WPSiteSync uses the mcrypt library to encrypt the password when authenticating with the Target site. And it looks like mycrypt is not configured with your PHP installation. You can install this with the following command:

    sudo apt-get install php5-mcrypt

    and then restarting your Apache server. If you need more help this might be useful: http://php.net/manual/en/mcrypt.installation.php

    Once mcrypt is installed, it should work fine. Please let me know if that works or if you still need help.

    Plugin Author ServerPress

    (@serverpress)

    Hi dhock194,

    We’re sorry to hear that you’re having trouble.

    To track this down, we need to see what is causing the error. Do you have access to the web server (Apache?) logs on the Source? The error logs should be reporting some information that will be useful finding out what is causing this. If not, adding WordPress error logging on the Source could help. You can add or update the following in your wp-config.php file:

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );

    Then, re-enter the configuration settings and save them. This should add some information to the log file located at wp-content/debug.log. Please send us the debug.log and the wp-content/plugins/wpsitesynccontent/~log.txt file via our support form at https://serverpress.com/contact/ and we will investigate. Also, please include your .org forum name, “dhock194”, so we know what it’s referring to.

    Thanks.

    Plugin Author ServerPress

    (@serverpress)

    Hi nk247,

    Thanks for the kind words. Now let’s see if we can get this working for you.

    The message “Target system did not respond with success code” happens when the Target site replies with an HTTP code that indicates an error. Something like a 500 error on the Target server. This can be caused by many things.

    Can you access the Apache error logs on the Target site? The error log should be reporting some information that will be useful in tracking this down. If not, adding WordPress error logging on the Target could help. You can add or update the following in your wp-config.php file:

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );

    Then, try Pushing the content with images to the Target. You should see some error messages in the wp-content/debug.log file on the Target. If you can send us the debug.log and the wp-content/plugins/wpsitesynccontent/~log.txt file from the Target site via our support form at https://serverpress.com/contact/ we can take a look at those. Also, please include your .org forum name, “nk247”, so we know what it’s referring to.

    Once we get that, we’ll be happy to take a look and help you resolve the issue.

    Plugin Author ServerPress

    (@serverpress)

    Hello Cesar,

    You are absolutely correct they are creating additional items beyond the post and postmeta. This would require an extension specific to their plugin(Events Manager). We will add this to the list of requested extensions.

Viewing 15 replies - 136 through 150 (of 234 total)