Error After Latest Update
-
I’m getting the following error when I open a page or post after the latest update. Any thoughts?
Cannot modify header information – headers already sent by (output started at /home/customer/www/domain.com/public_html/wp-content/plugins/custom-fonts/classes/class-bsf-custom-fonts-render.php:292) in <b>/home/customer/www/domain.com/public_html/wp-admin/admin-header.php</b> on line <b>9
-
Hi @chargeup,
Let’s try the basic troubleshooting by deactivating all of the plugins installed on your site and leave only this plugin active? If you get the error message disappear, then there’s a plugin conflict causes this.
What theme are you using? I will try it on my end. Also, what PHP version do you have, just in case it is related.
I look forward to hearing from you.
Kind regards,
Herman πI’ve already tried deactivating all plugins and switched to the basic 2023 theme. The error is still there.
I’m using Astra and I’ve tested on PHP 7.4, 8.0, and 8.1. The error is there for all versions.
Hope this helps.
This is also happening on all of my sites that are using this plugin. I have also done all the troubleshooting. It all points to this plugin. I didn’t see this thread, so I started a new one just a few minutes ago.
Hi @chargeup,
We are not able to replicate this on our end. Could you please reach out to us through our Support Portal, so we can take a look at this closer?
@juleshenson, I will ask the same thing on your thread.
Kind regards,
Herman π- This reply was modified 1 year, 3 months ago by Herman Asrori (BSF).
Yeah I’ll reach out over there. Just to give you a heads up, Brainstorm has almost the exact same error on another product of yours that you have known about for the better part of 8 months and have yet to apply a fix for.
I’ll put in a ticket for this plugin and hopefully you will be able to apply a fix sooner than later since these errors are pretty unsightly,
- This reply was modified 1 year, 3 months ago by chargeup.
Astra theme
Hi @chargeup,
If you need any assistance with our Astra theme, please start a new thread on its forum and we will try our best to help.
Kind regards,
Herman πIβve had a ticket out for this issue since May. They are aware of the problem, but have yet to release a fix.
Since the new error has to do with Custom Fonts thatβs why Iβve posted a new ticket here
Hi @chargeup,
I am sorry to bother you. Would you mind letting me know about what actually the issue is? I will follow this up to our team and see if we can expedite the fix.
Thanks,
Herman πHere is the original thread starter with the error. I’m not sure what the issue is. This is for BSF to figure out. This is error is being shown on everything single page/post when I open a page on the admin side of the website.
——————————————————————
Iβm getting the following error when I open a page or post after the latest update. Any thoughts?
Cannot modify header information β headers already sent by (output started at /home/customer/www/domain.com/public_html/wp-content/plugins/custom-fonts/classes/class-bsf-custom-fonts-render.php:292) in /home/customer/www/domain.com/public_html/wp-admin/admin-header.php on line 9
Hi @chargeup.
But, it is the same error you shared in your initial post?
Sorry if I didn’t clear enough, however, I was asking about the 8 months old Astra issue as you mentioned above.
Is there any miscommunication or am I missing something here?
Kind regards,
Herman πI just reposted the original issue above for you to look into. The other issue with Astra Pro is separate and I didn’t think it needed to be mentioned here in the plugin thread.
The Astra Pro thing a separate issue, but it also deals with that “Cannot modify header information β headers already sent by (output started…” error. That issue is obviously pulling from a file within that other plugin.
I just reshared the Custom Fonts error in the prior message to make sure you saw it and are aware of it.
Don’t take this the wrong way but Brainstorm Support is very frustrating and unfortunately I don’t have the energy or patience to work on another support issue with you. It takes weeks and weeks of deflecting the issue on another plugin or theme (even though I will show proof with everything deactivated that it’s coming from your product), telling me nothing is showing on your end and you are unable to replicate, then finally after weeks admitting there actually is an issue. At that point it could take months for a fix to actually be rolled out (if ever).
I have 4 open tickets with you with and when I ask for updates I get “Our developers are working on the issue. Thanks for you patience.” This typically goes on for weeks at the minimum, but usually much longer.
I do see another post for this exact same issue. Hopefully they have given you enough information to solve this
- This reply was modified 1 year, 2 months ago by chargeup.
Hi @chargeup,
Thanks for the clarification. I understand now. And yes, you were right, it’s not needed to mention it here. The forum’s rule doesn’t allow to discuss anything related to the pro version. Although I am not sure what the issue you were referring to is.
Regarding the Custom Fonts issue you reported, I hear you and I can understand the frustration. However, I must admit that, as of my last discussion with our team a few days ago, we were still unable to replicate this issue. I tried this myself on three different environments, fresh and existing installations. Zero!
By the way, I just wanted to mention that this plugin is completely free and open source. We initially created it for ourselves, but then we thought to make it available for public, so everyone can benefit from it.
If you happen to be a developer and would like to contribute to fixing this issue, we would love to have your contributions on GitHub.
However, don’t worry if you’re not a developer, we completely understand. We’ll see if we can manage our time to work on this, soon. In the meantime, please roll back this plugin to the version that you found worked well without any issues.
Kind regards,
Herman πHi @chargeup,
We recently released an update that contains the fix for this. Please update the plugin to the latest version, which currently is v2.1.3 and confirm the fix.
Kind regards,
Herman π
- The topic ‘Error After Latest Update’ is closed to new replies.