PHP notice since recent update to v2.0.9

Hi,

I’ve fixed that notice on 2.1.0 and I’ll push the update, probably tomorrow with a few more changes I’ve added.

That notice, occurs when there is a fallback for wp_remote_get.
Basically, we try to use the wordpress function for this, and fallback to curl if it fails (and that’s where the notice is occurring).

Unless you’re on localhost, this should never happen unless the first request was blocked… but regardless, thank you for letting me know, as it needed a fix.

—

As for the inline css option, what is the problem exactly?
Did you try to clear the cache on both the plugin options and whatever cache plugin you may use?

I use the inline css option in several sites, so I would like to know in more detail what happened (although it seems server related).

Kindly purge all wordpress caches and try again.

Hi Raul,
The update to v2.1.0 seemed to remedy the inline css issues, along with some server related changes to file permissions. I’ll let you know if that occurs again.

In the meantime, since updating to v2.1.1 two days ago my debug file has nearly 800 duplicate entries for your plugin. Here is the PHP notice it’s giving now:

PHP Notice: Undefined variable: header in wp-content/plugins/fast-velocity-minify/fvm.php on line 1556

It is the same exact entry nearly 800 times in just 2 days.

Thank you for all your help and awesome support of this plugin!

LL

This notice has been fixed on 2.1.2 now.

Those 800 times, are most probably the pageviews you received.

You will get one notice per pageview, whenever something like that happens, if your error reporting option is set to “notice”, instead of warning or above.

Thank you. I’ll update right now.

Funny thing is, my site is not yet open to the public so there is no traffic yet. No page views, beyond my own work and that was nowhere near 800 in that 48 hour period.

Those notices were posting every 3 minutes . . . really weird.

Appreciate all of your help. Thank you!

It could be that you either are viewing the site 800 times… or google is crawling the site without you knowing, or most probably, wp-cron is working on something.
You can look at the access.log (it should be next to the error.log)

I’m not viewing the front-end 800 times in 2 days. Those notices were posting like clockwork every 3 minutes or so.

I just installed WP Crontrol to see what all was running via the cron. There weren’t any crons scheduled to run every 3 minutes.

It just dawned on me as I’m typing this . . . I bet my uptime monitor is part of this. I have it set to check the site every 5 minutes. That, combined with my actual viewing of the front-end as I’m working would account for it all.

Thanks for all your help Raul!

This last update did remedy those notices.

Much appreciated,
LL