On Dec 1, 2014, at 10:00 PM, Ubence Quevedo that...@gmail.com wrote:
If that’s the case, how do I go about getting attention upstream regarding
this problem? This used to work perfectly at least back a few OS X releases
ago, it’s just with the last few releases that it’s suddenly stopped
On Dec 2, 2014, at 9:49 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Dec 1, 2014, at 10:00 PM, Ubence Quevedo that...@gmail.com wrote:
If that’s the case, how do I go about getting attention upstream regarding
this problem? This used to work perfectly at least back a few OS X releases
I have php53 thru php56 installed. My ide (PhpStorm) is pointing at php55,
for which I have xdebug installed. I could get xdebug to work fine from
inside the ide on a given script, or from the command line, but not from
the browser.
The PhpStorm folks finally asked me to send the output of
On Dec 2, 2014, at 10:04 PM, Jeff Greenberg wrote:
I have php53 thru php56 installed. My ide (PhpStorm) is pointing at php55,
for which I have xdebug installed. I could get xdebug to work fine from
inside the ide on a given script, or from the command line, but not from the
browser.
On Dec 3, 2014, at 12:05 AM, Jeff Greenberg wrote:
Regarding the handler, the php55-apache2handler port is installed, but there
is no mod_php55.so
Remember to Reply All. On my system:
$ port contents php55-apache2handler
Port php55-apache2handler contains:
Arrgh, sorry, it's late. I was looking at the port info output by mistake. I
just installed the handler and voila, file is there. I changed the lioadmodule
and I have xdebug now too. Thanks again!
On Dec 3, 2014, at 01:07, Ryan Schmidt ryandes...@macports.org wrote:
On Dec 3, 2014, at
