• Resolved mbouclas

    (@mbouclas)


    First of all, thank you for your work, this was a much needed plugin.

    Been using it since 2.6.1 and it rendered the content on REST calls just fine. Ever since v3 it no longer does so. Even on basic fields like content, let alone ACF fields.

    Sample output from 2.6.1

       "content": {
            "rendered": "<p><strong>as</strong> asas </p>\n",
            "protected": false
        },

    And from 3+

        "content": {
            "rendered": "<p>**as** asas </p>\n",
            "protected": false
        },

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Pierre-Henri Lavigne

    (@peter202202)

    Hello @mbouclas,

    Thank you for your kind words and glad the plugin is useful for users like you as well ??

    I appreciate the bug report, I’ve just released version 3.2.3 that should handle properly the filter that enable and disable the markdown parser with REST and the archive template. Indeed I found a few caveats. ??

    Feel free to give a try on your own when you can, and hope this will solve your case.

    Kind regards,

    Peter

    Thread Starter mbouclas

    (@mbouclas)

    Thank you for the prompt reply, it works as expected.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Since v3 not rendering on the REST’ is closed to new replies.