Skip to main content

Brizy Builder Still Injecting Custom Font (@font-face) References in Page Source After Font Removal - How to Fully Remove?

Dee Ferdinand

Hi Brizy Team,

I am reaching out regarding an urgent issue with a WordPress site (saranakonstruksi.id) built using the Brizy Builder. We have received a formal DMCA/copyright complaint from TipoType (the rights holder of the Marine Rounded font family) stating that references to their proprietary font files are still being served from the site.

Here is the situation:

- The physical .woff font files (MarineRounded-Regular.woff, MarineRounded-Bold.woff, MarineRounded-Black.woff) have been successfully deleted from the server (wp-content/uploads/2022/08/) and are now returning 404 errors.
- However, the @font-face CSS declarations referencing these files are STILL appearing in the page source HTML, embedded via a <style> tag with the ID "brizy-asset-upload-10--css".
- We have removed the custom font from within the Brizy Builder editor and replaced it with a standard font, and republished the pages.
- Despite these steps, the @font-face references persist in the rendered page source, indicating that Brizy is still storing and outputting these font declarations from somewhere in its database or asset cache.

The specific @font-face code still appearing in the page source is:

@font-face { font-family: 'rtsgfroyfsjzawsacjvxoqzxzzgjcfatxamt'; src: url(saranakonstruksi.id/wp-content/uploads/2022/08/MarineRounded-Regular.woff) }

(similar declarations exist for Bold and Black weights)

What we need help with:

1. How do we fully purge/remove a custom uploaded font from Brizy's internal storage so it no longer appears in the page source?
2. Is there a specific database table or Brizy asset record where these font declarations are stored that we can manually clean?
3. Is there a way to clear/reset Brizy's asset/font cache to force it to stop outputting these @font-face declarations?

This is a compliance-critical issue — our hosting provider has flagged this under a DMCA notice and we need to resolve it as soon as possible.

Site URL: saranakonstruksi.id
WordPress + Brizy WordPress Plugin

Thank you for your urgent assistance.

0

Comments

6 comments

Date Votes
  • KC George

    Hello Dee,

    Can we look at your WordPress dashboard to look for any references to MarineRounded font within the builder? Please add a new user to your WordPress Dashboard and send the following details to our email: communitysupport@brizy.io 

    Your email must include a link to this thread's URL, otherwise we will be unable to locate your support ticket. Please notify us in this thread when you send us the email.

    0
  • Dee Ferdinand

    I have deleted the files of the marine rounded and all the references. But it seems that if we look up the page view source code the artifact is still there even after I turn off and on brizy plugins 

    0
  • Dee Ferdinand

    I also have sent email 

    0
  • KC George

    Hello Dee,

    The three references to the MarineRounded font are in the HTML header of the page and not in the body. Have a look at https://jmp.sh/HjcLtKib. Let me discuss with my colleagues and get back to you on how to get rid of these referenes to the font files in the <head> section of different pages.

    Since the font file is already removed, shouldn't your website be considered compliant?

    0
  • Dee Ferdinand

    unfortunately the DMCA takedown is still happening if my client have trace of the marine rounded

    0
  • KC George

    Hello Dee,

    My colleague recompiled your pages and have cleared cache to get rid of the references to the MarineRounded font in the <head> section of your pages. Please check  

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question