zigpress

Thanks!

It’s probably worth checking the other forms as well (register, lost password, etc) to see if similar hooks need adding.

OK for me ??

That’s great, many thanks.

I have no idea. I inherited the site when I took on a new client. But there should always be validation before calling a function like array_merge, to avoid warnings like this.

Problem seems to be that a function get_plugin_data is documented as being available if is_admin is true, however this is not always the case.

Version 0.4.4 of ZigDashNote removes all reference to this function until a proper solution can be implemented.

The plugin was working on 10 of my sites and failing on one, probably with the same error you experienced. It now works on the site where it was failing.

Bug fixed in version 0.4.3. Apologies.

Thanks very much for the info. I’ll incorporate my custom theme’s version number into its stylesheet and script tags.

Can I make a feature suggestion for the plugin? You could have 3 checkboxes on the settings page: include images, include stylesheets, include scripts (all checked by default). That would determine what is fetched via the CDN and what is left alone to be fetched from the website. It would increase flexibility and versatility.

Thanks very much.

On the site in question we switched to Photon, but I’ve now tried Shift8 on a different site and it’s working fine – nice and fast.

OK. Time to uninstall Breeze and install something else.

I’ve now found that a WP site won’t run the cron scans either, the same as my CP sites. All other non-Shield crons run fine. I’ve read about the upcoming 7.0.4 – will that solve the issue?

There’s nothing in the PHP error log for the last two weeks.

Agreed it’s strange that the scans will run manually but not via cron.

When I have some more time I’ll add some temporary debug emails to the plugin code in the methods named by Crontrol to try and see what’s happening, but I won’t be able to do that for a couple of days at least.

Yes all the places that show info about the last scans are now updated.

Obviously I still need it to run via cron in order to roll out the plugin across more sites and maybe buy pro, so I’ll keep an eye on Crontrol as well as the plugin’s info pages.

Yes, both core file scanner and unrecognised file scanner appeared to work successfully when triggered manually on the scans page (each only took a couple of seconds though).

I’m running the latest Shield (7.0.2) on CP 1.0.0 beta2. I installed and activated it on 30th Jan at 22:13 (45 hours ago in my time zone so the daily ones should have run at least once).

Core files scanner and unrecognised files scanner are both enabled, and the hack guard module is enabled.

I know it hasn’t run the scans because the recent events log on the Shield dashboard says ‘not yet recorded’ and on the Scans page it says ‘never’.

OK, done that. The relevant crons I can see are:

icwp-wpsf-core-checksum-notification – next run in 3 hours xx minutes (so it should have run 21 hours ago)
icwp-wpsf-unrecognised-scan-notification – next run in 3 hours xx minutes (so it should have run 21 hours ago)
icwp-wpsf-daily – next run in 16 hours xx minutes (so it should have run 8 hours ago)

I’m not sure which one controls the core file scanner.

Crontrol gives me no warnings about problems, and in fact there is an UpdraftPlus cron which I know works because it emails me every day.

Crontrol says PHP crons can’t be created because the file editor is disabled, but I don’t think that’s relevant.