Note: this error occurs several times in the dashboard for the header and footer plugin.
Same error here on Mobile view.
Anyone?
Hi
I didn’t get it working in the end. An update to this plugin is what caused the issue. Zero responses from the community, and / or the support team so I bailed to another plugin, and stopped using this one on all my sites.
I’d recommend you ditch this plugin. Poor credibility.
I did so already.
Shame, but this is how many plugins are.
Gotta learn how to do things our way whenever possible.
Likewise – getting repeated php errors, culminating in a slew of other fatal errors so it’s causing some kind of memory issue too. And I haven’t updated to 4.7 yet. No updates for 5 months on this plugin, so I’m also guessing it’s been abandoned? 🙁
Especially frustrating when it has a listed user base of 100,000+ the kind of numbers where somebody’s usually pretty ‘on the case’, whether the original developer or enthusiastic user. Wish I had time to learn how to do this stuff…
um… 😉
-
This reply was modified 9 years, 4 months ago by
wwwolf.
Sorry Stefano – I’ve just seen a reply from you on another thread only a month ago, so not as ‘abandoned’ as I thought – hope you’re OK, and have a minute to look at this when you can
🙂
-
This reply was modified 9 years, 4 months ago by wwwolf.
I assume the author is just really busy 🙂 Talented developers are usually developing ten things at once!
It would be great to have a spare developer in the background. Where to find good developers with spare time though! 😉
This is also a problem for me. I just helped myself closing the if-condition half-way and commenting out the rest. Would be glad about a real fix, though. I guess, the only negative implication of my work-around is, that one cannot switch the mobile layout in the backend anymore.
Line 68 in plugin.php reads
if ($hefo_is_mobile ) { // && $hefo_options['mobile_body_enabled']) {
now. If you wanted to have no mobile layout, you’d probably go for
if (false) { // $hefo_is_mobile && $hefo_options['mobile_body_enabled']) {
Thanks @ditler. I was extremely grumpy with my previous response on this. I was obviously having a bad day!
Your work-around looks positive. Great result! 🙂
