Scott Cariss

Hi daymobrew,

Please raise this as an issue over at the plugins github page: https://github.com/l3rady/wp-updates-notifier

You may even create a pull request with your feature if you wish.

Scott

Hi Peterrodger,

Please be aware that this plugin your are using is not designed to be used in the way you are using it.

If you insist on using this plugin to do what you want then the only way to achieve what you are after would be to edit the plugins files itself.

To alter the email alert HTML you need to alter the function format_alert() found in /wordpress-file-monitor-plus/classes/wpfmp.class.php

Here you can remove the clear admin alert however this will remove the clear admin alert in the admin too.

Also from here you can change how the file location is shown. Instead of showing a absolute path to the file you could give a URI instead.

I would urge you to look for another plugin that is designed to do what you are after.

Kind Regards

Scott

What happens if you use the save settings with test email? Do you get the test email?

Version 1.4 is being worked on now: https://github.com/l3rady/wp-updates-notifier

It includes external cron usage and a method of setting other wordpress schedules that can be used in settings.

It would be a nice feature to have but it is not doable.

I don’t know any file system that stores the IP address of who made the change to the file last.

You need to enter the full path:

/full/path/to/folder/wp-content/backups/*

This plugin works fine with WP 3.5

If you look at the copyright information in a PHP file of my plugin it should have my email. You can email me over the code you’ve done and I’d be happy to add it to this plugin.

Scott

Ok I get you.

So basically if you are set to an hourly cron you will get notified every hour until the update is complete.

Yes this would have to be a setting that can be turned on and is off by default.

@hereswhatidid thanks reporting the glaring mistakes in my code with the missing variables.

I don’t know how I missed them in a past versions. I blame my IDE because this time round the mistakes where highlighted in bright red whereas before they were not.

As for the additional option you have added. Can you please explain some more as I’m not sure I fully understand.

Anyway new version of WPUN has been pushed to WP Org repository.

Scott

/home/[myaccount]/public_html/[mydomain]

Ok to be clear the above file check root will check for files only on the website it is running. If the website at that path is sandboxed and can only read and write it’s own files you wont be able to change the file check root further up the tree.

You could try this path: /home/[myaccount]/public_html but if this reverts back to default then your website only has access to read to it’s self.

As for ignoring dirs try the following:

/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/backupbuddy_backups*
/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/backupbuddy_temp*
/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/pb_backupbuddy*
/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/backupbuddy*

Make sure each entry is on their own line.

If the above doesn’t work try:

/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/backupbuddy_backups/*
/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/backupbuddy_temp/*
/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/pb_backupbuddy/*
/home/[myaccount]/public_html/[mydomain]/wp-content/uploads/backupbuddy/*

If this still doesn’t work then something with your webhost config is a-miss. Possibly a function not available or not enabled.

Please tell me what you currently have in File Check Root and I can recommend exactly what your exclude settings should be.

File Check Root is changeable option. The only reason why it would revert back to the default setting is if what you entered failed validation.

$sanitized_site_root = realpath( $input['site_root'] );
if( is_dir( $sanitized_site_root ) && is_readable( $sanitized_site_root ) )
    $valid['site_root'] = $sanitized_site_root;
else
    // Failed revert back to default

Again I re-iterate you need to include the full path to the folders you want to exclude. So this includes the document root setting you have.

Was the notification saying files were removed?

If you add a directory to ignore then the next scan will say the files where removed, however the scan after that will be clear from any changes or additions to those areas.