Brizy currently doesn't work with the Swirft Performance cache plugin

Stefan Rohlfing

• October 14, 2021 01:54
• Edited

Dear Brizy Team, 

When I noticed that all pages on my website I made with Brizy (pages designed with Thrive architect were not affected) had their styling removed when cashed, I contacted Swift Performance support.

This was their response:

=================

The issue is, that breezy <link> tags are not valid, and it breaks Swift DOM parser:

https://www.evernote.com/l/Aa6Bq2-tRQRP7I1281cvhTg8-Xj7jq8KWF4

 

<link> tags couldn't have class attribute(https://www.w3schools.com/tags/tag_link.asp). Please contact the plugin developer to fix this issue.

================

Is there a way to fix this issue on your end so that I don't have to exclude Brizy pages from being cached? 

Keep up the good work!

Best regards,

Stefan

Installed plugins mentioned above:

• Brizy, version 2.3.17 
• Brizy Pro, version 2.3.13
• Swift Performance, version  2.3.6.1

0

• 

  Mihail Stremenovskii

  • October 15, 2021 08:47

  Hello Stefan!

  Thank you for contacting us and letting us know about an issue with the Swift Performance plugin. 

  We created an internal ticket for our developer team to fix that. 

  Also, We contacted Swift Performance plugin developers too, you can check for it here: https://wordpress.org/support/topic/compatibility-with-brizy-plugin-8/

  Kind regards,
  Mihail

  0
• 

  Stefan Rohlfing

  • October 18, 2021 02:21

  Hello Mihail, 

  Thank you so much for digging into this issue and even contacting the Swift team!

  Kind regards,

  Stefan

  0
• 

  Stefan Rohlfing

  • December 01, 2021 02:48

  Hello Mihail,

  I'd like to ask if there have been any updates regarding this issue?

  Kind regards,

  Stefan

  0
• 

  Mihail Stremenovskii

  • December 01, 2021 11:55

  Hello Stefan!

  We are still waiting for the Swift Performance developers team. 

  So, unfortunately, I don't have any news for you.

  Kind regards,

  Mihail

  0
• 

  Stefan Rohlfing

  • December 02, 2021 03:14

  Hi Mihail,

  Thanks for your update. I contacted Swift again, asking them about the status of the issue. They've probably been working on it without talking much about it. 

  Kind regards,

  Stefan

  0

Please sign in to leave a comment.