View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001746 | Xdebug | Installation | public | 2020-02-14 20:01 | 2020-03-06 11:52 |
| Reporter | sfsccn | Assigned To | derick | ||
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 2.9.2 | ||||
| Summary | 0001746: Suggestion: have wizard show both CLI and apache php.ini paths | ||||
| Description | After following the wizard's instructions I got the apache version to work right away with Visual Studio Code's PHP Debug extension and its "listen" config. But the "launch script" config for CLI debugging didn't work - nothing happened. It took me a while to determine that on my system the php.ini path shown by the wizard, /etc/php/7.2/apache2/php.ini, is different that the one used for command line invocations: /etc/php/7.2/cli/php.ini. It would helpful to show both versions if they're different. Note the CLI path can be obtained from | ||||
| Tags | No tags attached. | ||||
| Operating System | Ubuntu 18.04.3 LTS | ||||
| PHP Version | 7.2.0-7.2.4 | ||||
|
|
I'm not sure how to do that, as the wizard only knows about the one that's being used. |
|
|
Good point, it only gets phpinfo() via web server. Then maybe have the wizard add a note to the user to check for a second cli-specific php.ini via php -r 'echo php_ini_loaded_file();'. |
|
|
I've added this to the wizard now, thanks! |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-02-14 20:01 | sfsccn | New Issue | |
| 2020-02-18 14:36 | derick | Note Added: 0005249 | |
| 2020-02-18 20:00 | sfsccn | Note Added: 0005257 | |
| 2020-03-06 11:52 | derick | Assigned To | => derick |
| 2020-03-06 11:52 | derick | Status | new => closed |
| 2020-03-06 11:52 | derick | Resolution | open => fixed |
| 2020-03-06 11:52 | derick | Note Added: 0005274 |
