Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Hi! Since you sent in an email and I replied there, and since the problem is being caused by a plugin inserting extra text in the xmlrpc.php file (in particular, something is adding

    <!-- ngg_resource_manager_marker -->

    to the file), I am marking this as resolved. Thanks!

    Thread Starter Jeroen

    (@jeroenonstenk)

    Well since the issue is still there, I don’t see any reason to mark this thread as resolved…

    I posted this also on the Nextgen support page: https://www.ads-software.com/support/topic/ngg_resource_manager_marker-added-to-xmlrpc

    I just deactivated all plugins on the website, and when I tried Publicize, all was ok. Then I activated them one-by-one and each time I tested Publicize. Again all was ok. The last plugin I activated was Nextgen, and then Publicize ‘broke’.

    Again the same error code. So I guess there is an issue with Jetpack’s Publicize and Nextgen Gallery.

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    Hi Jeroen,

    Richard marked it as resolved since the issue is due to another plugin adding something to xmlrpc.php—not something within Jetpack’s control. Additionally, with having an e-mail communication as well, It is problematic having multiple conversations concerning the same site/problem, so we try to mark as resolve all but one to centralize conversations.

    I am following the NGG thread you mentioned and will reply there if Jetpack’s involvement is needed.

    Cheers!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Publicize Not Connecting – Error code: -32700’ is closed to new replies.