Image php5.6-apache. debbuging my code - apache

I'm using docker-compose to create two containers connected between them. (the images are php5.6-apache and mysql).
Everything is running OK. my problem is when i want to start working. i cant see the typical errors in php. (i always worked on xampp). i've seen a lot of documentation how to enable the debugs but i cant find a solution. I tried to find php.ini but apparently it is not in the apache container. I tried to install xdebug as the documentation...
anyone know how to do it?
I need to do it in php 5.6 as my application doesn't work with newer versions.

Related

ActiveMQ :Web demo not working

I am a newbie to activemq stuff.I tried to run the web demos using the steps mentioned on the site http://activemq.apache.org/web-samples.html and I am getting 404 not found.I googled for the same and tried digging through the logs as well .But my bad , I could not get any clue even from the logs. I even copied the demo folder to the webapps folder but some of the links don’t work.
Kindly help me out with the steps to run these web demos
.\bin\activemq.bat start xbean:examples/conf/activemq-demo.xml - works perfectly fine on Windows 10. start was missing in other answers.
I encounter similar issue in Windows Platform.
The documentation at Getting Started Page or Web Sample Page states how to start the ActiveMQ with examples in Linux/Unix Platform.
There is an minor issue in activemq.bat file as stated in Apache's JIRA. Put double quotes around %ACTIVEMQ_CONF%\login.config fixes this issue.
To Start ActiveMQ in Windows in unzipped apache-activemq-5.9.0 folder use the below command,
.\bin\activemq.bat xbean:examples/conf/activemq-demo.xml
I was able to open http://localhost:8161/demo/ without any Issue.
I ran into the same issue. It seems like
bin\activemq console
is not an option on Windows. I finally got around it by using:
bin/activemq start xbean:examples/conf/activemq-demo.xml
http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-ActiveMQ5.9onwards

problems deploying openMRS.war to glassfish v.2

I'm trying to deploy openMRS v.1.9.2 to a local VM running CentOS & Glassfish 2 for work. Unfortunately, I could not get it to work. Normally, I just download the standalone found at source forge. I just double-click the jar, and I'm good to go.
I normally just SSH into the the VM, so I first tried doing everything through a terminal. Here are the steps I took:
Using wget, retrieve the .zip
Create a dir (I just called it /openmrs), cd into the new directory, and then expand the .zip.
cd into the directory.
At this point, there are two options to start openMRS.
Run the bash script: ./run-on-linux.sh
Run the .JAR: java -jar [insert_jar_name].jar -commandline
When I run the .JAR, I get a stack trace.
When I try to run the bash script, I get another error.
Anyways, I thought I found a potential solution in an openMRS JIRA ticket, but it seems aimed at Glassfish 3, and not Glassfish 2 (which is what I need to use).
I then tried deploying the .WAR via the Glassfish admin UI. I thought it would work, but after going through the steps of selecting a language, whether or not to use demo data, etc. I received this.
Does anyone have experience deploying openMRS to Glassfish 2.1.1? Unfortunately Glassfish 3 doesn't seem to be a realistic option. I would really appreciate any help here. Thanks.
Although it doesn't solve my problem of not being able to successfully deploy openMRS to an instance of Glassfish v.2, I did manage to get myself further by just installing MySQL on the VM. Our work machines are all set up for postgres, so I think should have guessed earlier that not having a MySQL server installation was the problem.
Here is a tutorial I used to install MySQL

PHP PDO shows "no value"

I've seen many questions describing this issue but none tackling the solution.
Last night I updated PHP from 5.3.2 to 5.4.6 and all of the sudden PDO started acting strange and showing that no drivers were available.
I have necessary DLL (php_pdo_mysql.dll) in ext directory
In php.ini both PDO and database-specific extension are enabled
The following code acts differently when executed from terminal/cmd and from browser:
print_r(PDO::getAvailableDrivers());
in terminal/cmd it shows appropriate driver list while in browser shows empty array.
All this led me to believe that something was not quite right with Apache installation (which is still at 2.2). I've installed version 2.4 just to be sure but nothing has changed.
When called, phpinfo() shows correct php.ini path but is there anything else that could affect proper PDO loading?
Thanks in advance!

Trying to transfer older version of mediawiki to new server

So, in college I had a Debian server which used to host a wiki, with mediawiki version 1.9. This server stopped working, and all I have now is its HD. I want to transfer this wiki to a new server, which also runs Debian, but I can't do that with Debian's current stable version of mediawiki, 1.15, because it is not possible to transfer a wiki to another version of mediawii.
So, my idea is to install mediawiki 1.9 on the new server, and then move the wiki. But I am having problems with installing it.
When I go to http://my_hostname/config/index.php, to configure the new wiki, so that I can transfer the other one, I get the following message, and nothing happens:
Checking environment...
Please include all of the lines below when reporting installation problems.
PHP 5.3.3-7+squeeze8 installed"
I really don't have a clue on what is wrong. ANY help would be greatly appreciated!
Like you commented yourself, it would certainly be worth a try to using your existing configuration. The configuration is typically some site preferences and database configuration, so make sure dat your database is setup in the same way as before.
Regarding your configuration problems, maybe php filters away the errors. You can check this by searching for error_reporting in your php.ini.
Just follow the instructions at http://www.mediawiki.org/wiki/Manual:Upgrading. Probably no point in trying to install at MediaWiki 1.9.
You may want to do a clean install of MediaWiki 1.18.1 first just to make sure your system is ready, all dependencies met, etc.

Joomla Mootools file getting truncated

I am trying to run Joomla on my local machine. I have installed wamp 2.0 and everything installed ok with it and I managed to see it running. I have now come to install Joomla 1.5.18 but I am having a problem with the mootools file on the installation wizard.
When running through the installation process in FireFox with firebug turned on I get errors about the mootools file missing a }. When I view the file through windows explorer it is complete and everything is fine with it but when I click on the error in firebug to see the error the file is truncated which I assume is why it is not working and complaining about a missing }. To test the file I created a test page which pulls in the same mootools file and this works fine (running locally and not through Joomla ).
Does anyone know why this is happening and how to fix it? I think it must be a problem with wamp as like I said the file is fine and runs ok if I run it from the file system, however I know nothing about servers so this is a guess. Maybe a limit on the size of a file which can be returned as the mootools file is around 7000 characters long.
I have tried un-installing both Joomla and Wamp but none this has not worked and I still get the same error. Thanks
I'm just curious, have you tried installing a newer version of Joomla? 1.5.8 is a little bit old and you may have better luck using something a version or two newer. Alternately speaking, if you're not a big fan of installing WAMP and then manually installing Joomla, you can use a Bitnami Joomla stack. Basically, Bitnami installs Apache, mySQL, PHP, and Joomla all in one quick and easy install.
I hope that some of this helps!
I would suggest that your problem is not with the Mootools package but with your template or modules that are loaded in. Can you turn off all of your modules and reenable them one by one until you see the error again?