Custom CSL broke after CURL fix

  • Resolved adonehey

    (@adonehey)


    7 years, 9 months ago

    After the most recent updates, the shortcode returns no results when a csl file is specified. After looking through other recent posts about csl files and comparing to a backup version of the wp-mendeley.php file from January, I replaced the updated formatdocument function with the old CURL code and returned functionality.

    My csl files are on the same server, but in a public folder outside of the wp-content. The same blank results was given with csl files on different servers. There was nothing obvious in the readout with the debug on.

    I’m not really looking for any immediate assistance, as reverting to the old code solved my issue. I wanted to put it out there that this update/fix, while it may have helped some people, it seems to have caused some other conflict for my setup.

Viewing 1 replies (of 1 total)
  • Plugin Author kochm

    (@kochm)

    Could you pin down the problem a little bit? That is because I cannot reproduce the issue – in my installations CSL support works well with the newest version of the plugin – even after emptying all caches etc.

Viewing 1 replies (of 1 total)
  • The topic ‘Custom CSL broke after CURL fix’ is closed to new replies.