Error, showing up at the top of every panel page

SETTINGS
Always Latest () – (nothing else shows in dropdown but that)
jsDelivr
Minified CSS: Yes
Remove Existing: No

HOST
HostGator

FONTS
Yes

I’m also getting this…

Warning: Invalid argument supplied for foreach() in /public_html/wp-content/plugins/better-font-awesome/better-font-awesome.php on line 222

Warning: Cannot modify header information – headers already sent by (output started at /public_html/wp-content/plugins/better-font-awesome/better-font-awesome.php:222) in /public_html/wp-includes/pluggable.php on line 1121

and sometimes this..

Warning: implode() [function.implode]: Invalid arguments passed in /public_html/wp-content/plugins/better-font-awesome/better-font-awesome.php on line 401

Screen Capture

Hi everyone,

Thanks for your patience, I’ve been out of town these last 2 weeks and am just gettin back to the issues list here.

More and more, it’s looking like this is an issue with the server timing out when trying to fetch the latest version of Font Awesome from the CDN. I’ll be working on an update over these next few days which should hopefully solve this issue, however since it’s a tough one to reproduce, I would love your help once the update is available, if/when any other warnings arise.

Thanks again for your patience, and stay tuned for an update.

All the best,
Mickey

Welcome back,

I agree with you, I too think it is a hosting environment issue.
The only host I have been using on my end is Hostgator (not recommended) due to massive datacenter stability issues.

Happy to help where I can though,
Jeffrey

downloaded latest version and got this errors:

Warning: sort() expects parameter 1 to be array, null given in /home/admin/domains/xxxxx/public_html/xxx/wp-content/plugins/better-font-awesome/better-font-awesome.php on line 180

Warning: implode() [function.implode]: Invalid arguments passed in /home/admin/domains/xxxxx/public_html/xxx/wp-content/plugins/better-font-awesome/better-font-awesome.php on line 398

have it also installed on my other site on other host and there no problems ??

So i have two exact the same installs 1 on a shared hosting and 1 on a vps. The vps is giving the errors! When i tried to activate it on the vps it gave me a error “the plugin does not have a valid header”! Then i deleted it and uploaded it by FTP and activating worked. Then i got the error mentioned above. Its frontend & backend.

Hi Jeffrey,

Apologies for the issues you’ve been facing. Two updates on this front:

1. Unbeknownst to me until just now, v0.9.6 included some code that was not meant to be included, which was an error on my part. I’ve uploaded v0.9.7 which includes a fix. This was causing the plugin to throw an error on <i>all</i> installs, which is indeed not good at all. It took me a while to track this down as a few users (like yourself) were also experiencing the same errors as a result of wp_remote_get() timing out. v0.9.7 repairs the first issue, however the timeout issue is what I’m currently working on. . .

2. As mentioned, I am currently working on an update that is intended to ensure that you never receive these errors again, and that Font Awesome loads no matter what. This update involves a pretty thorough reworking of the plugin and should be much more reliable. I’ll make sure to include clear notes in the update notification when it goes out.

Thanks so much for your patience and continual feedback ??

Mickey,

I’m impressed that you were able to figure out such a seemingly random yet persistent issue. Thank you!!!

This is getting to be a bit ridiculous. Now I am getting this error, and it persists on the front end and back end:

Warning: require_once(/home/null/public_html/null-content/plugins/better-font-awesome/Titan-Framework/class-admin-notification.php): failed to open stream: No such file or directory in /home/null/public_html/null-content/plugins/better-font-awesome/Titan-Framework/titan-framework.php on line 22

Fatal error: require_once(): Failed opening required ‘/home/null/public_html/null-content/plugins/better-font-awesome/Titan-Framework/class-admin-notification.php’ (include_path=’.:/opt/php54/lib/php’) in /home/null/public_html/null-content/plugins/better-font-awesome/Titan-Framework/titan-framework.php on line 22

I love the plugin, and you seem very quick to address issues, but it keeps knocking sites offline.

Hi again Mike,

First things first, I am working on a pretty revamped version of this plugin that will provide numerous fallbacks to avoid timeouts and other issues that have been throwing errors. I know it’s hard to wait when things aren’t working right, but I did want to let you know this was in the works.

Secondly, I’m really sorry for the trouble, I’ve no clue what’s going on as the latest version of the plugin works fine for me (even with WP_DEBUG on as well).

The weird thing about the error you’re seeing is that it’s referencing a file path that doesn’t make any sense – the path includes “null” and “null-content”, which don’t seem right at all. I’m wondering if something went wrong server-side during the install process by some chance. Any chance you’d be willing to try reinstalling? Just for reference, the one line of code that is throwing this error is from an embedded framework in the plugin that I didn’t touch at all:

defined( 'TF_PATH' ) or define( 'TF_PATH', trailingslashit( dirname( __FILE__ ) ) );

Essentially, the basic php function dirname( __FILE__ ) is returning a path that appears to be broken, which makes me wonder if the plugin install just didn’t quite work correctly. If you could try re-installing, that would clarify this one.</p>
<p>That said, the problem may be something else entirely – it’s just hard for me to debug when I don’t see the issue on my side. Can you explain if there were any steps you took other than just clicking the update link for the plugin? Is there actually a “null-content” directory on your install? If not, any idea why trailingslashit( dirname( __FILE__ ) ) would be returning that directory?

I truly appreciate your patience and understand your frustration. I’ll do my best to get to the bottom of this and fully test our new update to assure that it resolves these issues. Would love to give you an acknowledgment in the plugin about page as well, for all your help, if you’re okay with that.

Thanks Mike.

Thanks for your response. As it turns out, the problem was related to a bad update. It looks like I didn’t get all of the necessary files so I was receiving the error.

I uninstalled the plugin and re-installed it fresh. So far it’s working fine, no errors.

This problem can most likely be attributed to infiniteWP rather than www.ads-software.com or better font awesome.

By the way, the “null” directories were simply my attempt to obfuscate any personal details. Sorry for confusion.

I’m going to mark this as resolved y’all!

Yes resolved! ??

And resolved. . .