Hi all,
We try to register our plugin using AppConfig. As the plugin needs a special PHP module, we try to use the *phpHandler* key to avoid tainting the original php.ini file.
We have the following config file :
We have created the directory /usr/local/cpanel/3rdparty/etc/foo and copied the original php.ini in it.
The AppConfig registration succeed and the plugin appear in WHM (Home » Development » Apps Managed by AppConfig) but nothing is displayed in the *PHP Config* column and when running the plugin, the custom php.ini file is not used.
We then have a look at how is this implemented by *phpmyadmin*, *roundcube*, etc. And do the same, that mean create a link */usr/local/cpanel/3rdparty/etc/foo/php.ini* to */usr/local/cpanel/3rdparty/php/54/etc/foo/php.ini* (which is not what is in the documentation). But the result is the same, our custom php.ini is not used.
Is there a way to see what exactely do *register_appconfig* like a -d/--debug flag ?
Or maybe could we do something manually after have run *register_appconfig* to make this works ?
Thanks in advance for any information.
Philippe Ney
We try to register our plugin using AppConfig. As the plugin needs a special PHP module, we try to use the *phpHandler* key to avoid tainting the original php.ini file.
We have the following config file :
Code:
name=foo
url=/foo/
service=whostmgr
user=root
phpHandler=foo
acls=all
displayname=Foo plugin
entryurl=../foo/index.php
The AppConfig registration succeed and the plugin appear in WHM (Home » Development » Apps Managed by AppConfig) but nothing is displayed in the *PHP Config* column and when running the plugin, the custom php.ini file is not used.
We then have a look at how is this implemented by *phpmyadmin*, *roundcube*, etc. And do the same, that mean create a link */usr/local/cpanel/3rdparty/etc/foo/php.ini* to */usr/local/cpanel/3rdparty/php/54/etc/foo/php.ini* (which is not what is in the documentation). But the result is the same, our custom php.ini is not used.
Is there a way to see what exactely do *register_appconfig* like a -d/--debug flag ?
Or maybe could we do something manually after have run *register_appconfig* to make this works ?
Thanks in advance for any information.
Philippe Ney