Issues with by line, canonical, client-host connection extra custom field entry

  • Bub

    (@jdenning47)


    8 years, 8 months ago

    I really want this plugin to work and will continue to use it even with the problems I list. I have control over both the client and server so I can work around these issues.
    Issues for me:
    The original post ‘by line’ doesn’t get syndicated.
    When I look at page source the canonical leaves out part of the URL (e.g. https://www.mysite.com/mycategorie/mypost becomes https://www.mysite.com/mypost). This then makes a 404 error. This requires manual changes in the client.
    When cron fires in the client and tries to get new posts I often don’t get a download for several attempts. Until I get a successful download I repeatedly get emails that say “This is a message from your Content Syndication Toolkit wordpress plugin. There was an error when trying to get new syndication posts from the content creator. All posts in this import will need to be reimported. Please login to wordpress and make a manual content pull request using the plugin tools under “Settings -> Content Syndication” in the wordpress admin area.
    Here is the error message: “Problem contacting the server. Please confirm your API Username and Password are correct. Error: transport error – HTTP status code was not 200 CODE: -32300    ” – Please allow control of emails.
    Lastly, my client post custom fields are repeatedly loaded with many duplicate ‘pcst_canonical_permalink’ and ‘prso_synd_toolkit_ID’.

    https://www.ads-software.com/plugins/content-syndication-toolkit/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author ben.moody

    (@benmoody)

    Hi

    First, the canonical link should point back to the original post on the master site. The master plugin uses get_page_link() to generate the canonical link back to the original post.

    Second. I’m not familiar with server error -32300. Do the reader plugin return this ever time you try to pull content or is it intermittent? The plugin is trying to make an xmlrpc request to the master site and the master site server is returning the error code -32300. Can you ask you host as to what this code represents and why the master server is returning it as opposed to code 200

    Plugin Author ben.moody

    (@benmoody)

    HI

    After some research I think i’ve found the cause of the 32300 error.

    It appears that this is due to a PHP error on the master server relating to php memory:

    https://mu.www.ads-software.com/forums/topic/5997

    Ask your host to increase your php memory limit to something higher say 30 or 50 MB

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Issues with by line, canonical, client-host connection extra custom field entry’ is closed to new replies.