Recently my site http://www.vanzeeland.net produces messages "Warning: ignore_user_abort() has been disabled for security reasons in /sites/vanzeeland.net/www/includes/session.php on line 272" Apparently my provider has updated PHP security settings. It can not(doesn't want to) set those settings back. Is there a possibility to adjust PHPGedview so that those warnings don't show up?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You're using an old version of PGV. For security and stability reasons, you should consider upgrading to the most recent version available.
Upgrading will NOT solve your problem.
PGV is trying to tell the PHP system that the user is allowed to cancel whatever process within PGV is taking too much time. I don't see how this function should be disabled "for security reasons". Your service provider is being unreasonable here.
What other essential functions have been disabled "for security reasons"? Ask for this list, and post it here. You might need to look for a different provider.
However, PGV should work OK without needing to run that disabled function. You will need to modify file "includes/session.php" to add a couple of forward slashes to the beginning of the line in question. This will transform that line into a comment and thus avoid the error. Note that the line number is different for different versions of PGV.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
<<What other essential functions have been disabled "for security reasons"? Ask for this list, and post it here>>
You should be able to find out which functions are disabled without contacting your host. From the PGV admin page, follow the link to "PHP Information". In the "core" section, there will be an entry for "disable_functions".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd look for a different hosting company because of "no PDO support".
There should be no problem with any of the other disabled functions, except for "set_time_limit" since PGV doesn't use any of them. "set_time_limit" is used while editing language files. If you're not planning to do any of that, you should be OK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most of these restrictions are fairly common. I've not seen anyone block ignore_user_abort() before. PGV uses it to *allow* a user to cancel a process. e.g. if the user cancels a slow page request, the server process will die immediately. This is a good thing - it frees up server resources.
It can also be used to prevent a user from cancelling a script. This is useful if you are doing processing that should continue without interruption (e.g. moving an image *and* its thumbnail from one location to another).
Since your host has blocked set_time_limit(), a process cannot run for an extended period, and this restriction doesn't really gain anything.
In summary, this is not really important. PGV just calls this function for "good practice". It is not absolutely necessary. As Gerry said, just comment out the line in session.php, and you'll be fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Recently my site http://www.vanzeeland.net produces messages "Warning: ignore_user_abort() has been disabled for security reasons in /sites/vanzeeland.net/www/includes/session.php on line 272" Apparently my provider has updated PHP security settings. It can not(doesn't want to) set those settings back. Is there a possibility to adjust PHPGedview so that those warnings don't show up?
You're using an old version of PGV. For security and stability reasons, you should consider upgrading to the most recent version available.
Upgrading will NOT solve your problem.
PGV is trying to tell the PHP system that the user is allowed to cancel whatever process within PGV is taking too much time. I don't see how this function should be disabled "for security reasons". Your service provider is being unreasonable here.
What other essential functions have been disabled "for security reasons"? Ask for this list, and post it here. You might need to look for a different provider.
However, PGV should work OK without needing to run that disabled function. You will need to modify file "includes/session.php" to add a couple of forward slashes to the beginning of the line in question. This will transform that line into a comment and thus avoid the error. Note that the line number is different for different versions of PGV.
<<What other essential functions have been disabled "for security reasons"? Ask for this list, and post it here>>
You should be able to find out which functions are disabled without contacting your host. From the PGV admin page, follow the link to "PHP Information". In the "core" section, there will be an entry for "disable_functions".
Thx for the responses. I have adjusted the coding so that the messages doesn't show. The list of disabled functions is:
Local Value
apache_child_terminate, apache_get_modules, apache_note, apache_setenv, dl, exec, passthru, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, system, popen, pclose, virtual, set_time_limit, ignore_user_abort, pcntl_alarm, pcntl_exec, pcntl_fork, pcntl_getpriority, pcntl_setpriority, pcntl_signal_dispatch, pcntl_signal, pcntl_wait, pcntl_waitpid, pcntl_wexitstatus, pcntl_wifexited, pcntl_wifsignaled, pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig, posix_access, posix_ctermid, posix_get_last_error, posix_getcwd, posix_getegid, posix_geteuid, posix_getgid, posix_getgrgid, posix_getgrnam, posix_getgroups, posix_getlogin, posix_getpgid, posix_getpgrp, posix_getpid, posix_getppid, posix_getpwnam, posix_getpwuid, posix_getrlimit, posix_getsid, posix_getuid, posix_initgroups, posix_isatty, posix_kill, posix_mkfifo, posix_mknod, posix_setegid, posix_seteuid, posix_setgid, posix_setpgid, posix_setsid, posix_setuid, posix_strerror, posix_times, posix_ttyname, posix_uname, lchgrp, lchown, lstat, symlink, link, readlink, linkinfo, syslog, openlog
Master Value
apache_child_terminate, apache_get_modules, apache_note, apache_setenv, dl, exec, passthru, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, system, popen, pclose, virtual, set_time_limit, ignore_user_abort, pcntl_alarm, pcntl_exec, pcntl_fork, pcntl_getpriority, pcntl_setpriority, pcntl_signal_dispatch, pcntl_signal, pcntl_wait, pcntl_waitpid, pcntl_wexitstatus, pcntl_wifexited, pcntl_wifsignaled, pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig, posix_access, posix_ctermid, posix_get_last_error, posix_getcwd, posix_getegid, posix_geteuid, posix_getgid, posix_getgrgid, posix_getgrnam, posix_getgroups, posix_getlogin, posix_getpgid, posix_getpgrp, posix_getpid, posix_getppid, posix_getpwnam, posix_getpwuid, posix_getrlimit, posix_getsid, posix_getuid, posix_initgroups, posix_isatty, posix_kill, posix_mkfifo, posix_mknod, posix_setegid, posix_seteuid, posix_setgid, posix_setpgid, posix_setsid, posix_setuid, posix_strerror, posix_times, posix_ttyname, posix_uname, lchgrp, lchown, lstat, symlink, link, readlink, linkinfo, syslog, openlog
I have 4.2.1 installed by the way because 4.2.3 requires PDO enabled which is not at my provider transip.nl
I'd look for a different hosting company because of "no PDO support".
There should be no problem with any of the other disabled functions, except for "set_time_limit" since PGV doesn't use any of them. "set_time_limit" is used while editing language files. If you're not planning to do any of that, you should be OK.
Most of these restrictions are fairly common. I've not seen anyone block ignore_user_abort() before. PGV uses it to *allow* a user to cancel a process. e.g. if the user cancels a slow page request, the server process will die immediately. This is a good thing - it frees up server resources.
It can also be used to prevent a user from cancelling a script. This is useful if you are doing processing that should continue without interruption (e.g. moving an image *and* its thumbnail from one location to another).
Since your host has blocked set_time_limit(), a process cannot run for an extended period, and this restriction doesn't really gain anything.
In summary, this is not really important. PGV just calls this function for "good practice". It is not absolutely necessary. As Gerry said, just comment out the line in session.php, and you'll be fine.