I tried them all, those fixes, do not work correctly they even create new problems.
I did get SiteMonitor to write to a log folder by adding another entry like DIR_FS_ADMIN2
and editing some files relating to ref, log etc I then exclude logs and I never get false
emails anymore. what a pain in the ... finding those path locations
I asked you in a earlier post to simply let me know how to set a manual path for a log folder,
you could have saved me hours by just letting me know where the 4 or 5 quick edits where at.
Common, you knew exactly where they where, as well as a tip to start with DIR_FS_ADMIN paths.
remember the only reason I even asked about that in the first place was because of a bug in
the program code.
Whenever you get around to fixing things in the contrib download, its a good idea to give users a
choice to set a folder path for instances of log, ref and config files.
You should know more then anybody
Static built in paths that relay on default folder settings are asking to be hacked or rendered
useless. I have removed the admin settings altogether and just use it with cron. to many errors
especially running sitemonitor_hacker_cron.php, I also read some of your replays to posters stating
its server related, I tested on at lest 3 different linux servers with the same results.
and that image folder contains .php files, error message, every time the update page displays, is
a problem in the code not, the server.
PF