• Resolved rpp

    (@rpfaffenbach)


    Version 1.2.6 creates massive Apache Errors in every existing FAQ
    This Version generates mixed content: html and \n (sometimes also \r] instead of <br>

    Example:

    ] [STDERR] content: <p><!-- wp:paragraph --></p>\n<p>Mein gesamtes Flechtmaterial beziehe ich von Materialh..ndler aus Oberfranken und teilweise auch aus Frankreich.</p>\n<p><!-- /wp:paragraph --></p>\n<div class="wp-block-media-text is-stacked-on-mobile">\n<figure class="wp-block-media-text__media"><img class="wp-image-13171 " src="https://www.kreativefinger.de/wp/wp-content/uploads/2021/04/20170121_162611_1280.jpg" alt="20170121_162611_1280" width="966" height="724" /></figure>\n<div class="wp-block-media-text__content">..</div>\n</div>\n

    After Rollback to v1.2.5 the text is always OK

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Essekia

    (@essekia)

    @rpfaffenbach Looking into this.

    Is the FAQs displayed in the frontend appearing fine?

    Thread Starter rpp

    (@rpfaffenbach)

    Thanks for asking
    Yes, the FAQs are displayed correctly in the frontend. Tested with the latest Chrome, Firefox, Edge for desktop and mobile.

    With version 1.26, the Apache error log is flooded with the information from the FAQ. And it is probably because the delivered pages always contain \n and sometimes \r instead of pure HTML.

    If you need further information, please do not hesitate to contact me.

    Plugin Author Essekia

    (@essekia)

    @rpfaffenbach Released an update.

    Thread Starter rpp

    (@rpfaffenbach)

    It looks very good now. I can no longer find any errors after updating to version 1.27. Thank you very much for the quick solution

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.