Bonjour;
On peut avoir les logs ?
Note: ispCP 0.0.7 ???
Bonjour;
On peut avoir les logs ?
Note: ispCP 0.0.7 ???
For me we must not longer continue to allow arbitrary mount points for subdomains/aliasses. It's pain in ass to maintain. It's better to provide fixed tree, and if an user want redirect a subdomain to a specific directory, we can provide redirection.
We can also provide specific subdomain directory redirection to another subdomain directory. Same for aliasses.
For the last, I'll add same if we continue to allow arbitrary mount points.
Hello folks ;
Normally, both issues are now fixed. Please test.
Please, retry (update) with latest trunk. It's now normally fixed.
Fixed in trunk (r5209).
I can reproduce it manually on:
root@kvm217175:~/daemon# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.04
Release: 11.04
Codename: natty
root@kvm217175:~/daemon#
Daemon compilation output:
root@kvm217175:~/daemon# make clean imscp_daemon
rm -f *.o *~ imscp_daemon
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 imscp_daemon.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 message.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 daemon_init.c
daemon_init.c: In function ‘daemon_init’:
daemon_init.c:19:7: warning: ignoring return value of ‘chdir’, declared with attribute warn_unused_result
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 say.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 signal-handlers.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 receive_data.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 send_data.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 take_connection.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 send_line.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 recv_line.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 helo_cmd.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 helo_syntax.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 lr_cmd.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 lr_syntax.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 bye_cmd.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -c -g -O2 bye_syntax.c
gcc -ansi -Wall -Wstrict-prototypes -pedantic -g -O2 -g -O2 imscp_daemon.o message.o daemon_init.o say.o signal-handlers.o receive_data.o send_data.o take_connection.o send_line.o recv_line.o helo_cmd.o helo_syntax.o lr_cmd.o lr_syntax.o bye_cmd.o bye_syntax.o -o imscp_daemon
strip -s imscp_daemon
Compilation done
root@kvm217175:~/daemon# echo $?
0
Note: Seem that it's wrong error management in installer. For me, warnings from compilation that doesn't break build process must be hidden... Right now, it's better without any warnings and so, I'll fix in daemon source directly. The warning doesn't occurs on Debian Squeeze that explain why Daniel was not see it.
BTW: If the warning doesn't break the setup/update, you can ignore it.
English please. Official support from (active) development team members is only provided in English.
Thanks you.
Edit: The better to follows (I thinks) :
If you are already using PHP 5.3.x and you’ve just upgraded to Typo 4.3 or greater, Typo3 might start throwing exceptions where previously everything had worked out just fine.
This is because the Typo3 developers chose to take some of the error handling into their own hands and raise exceptions for certain errors. Now these “certain errors” for which exceptions are raised include E_DEPRECATED, and as a bunch of functions have been deprecated in PHP 5.3, well, you know where I’m going with this.
Fortunately, there is a configuration variable which allows to change the default behavior:
$TYPO3_CONF_VARS['SYS']['exceptionalErrors']
The default value (defined in “t3lib/config_default.php”) is
To disable the deprecation exceptions, just add a ^ E_DEPRECATED like this (the line goes in your localconf.php file):
Ref: http://x3ro.de/php-53-typo3-43-t3liberrorexception/
Edit: Seem that is for typo >= 4.3 but normally, you must now got the idea to how resolve the issue without installing older php version.
Like joximu say: Deprecated warnings can be disabled easily.
Found on google :
http://www.typo3forum.net/forum/165371-post14.html
If not, you will have shit like : http://www.cargo-operation-centre.de/function.session-start
gOOvER : I suggest you to not lost your time with this kind of man...