![]() Some are of a general nature that can affect the overall environment and some are more specific to a certain aspect of the IDE. In the following sections you will learn about much of the systemwide preferences that can be controlled in this IDE. We deal with all other preference settings that may be adjusted depending on a certain topic inside that specific context. Throughout the remainder of this chapter, we first discuss systemwide preferences and provide some detailed examples of them and then describe some specific preferences that affect how PHP is handled within Zend Studio for Eclipse itself. We guide you through most of these options in this chapter, but we merely mention some of these differences as such. Some preferences have systemwide ramifications and some are quite specific to a certain topic or process. ![]() However, it's not too difficult to back yourself out of any corners that you may find yourself in.īefore we get too close to the details of the preferences, here are just a few words about the nature of the preferences. If you're not careful, you can get yourself into some trouble using this option. Under the Window menu, there is an item that opens up this Pandora's box of options: Preferences, located at the bottom of the menu displayed when you select Window. Zend Studio for Eclipse is no exception however, there are some differences between the Zend Studio for Eclipse product layer itself and the Eclipse foundation on which it is built. Learn More Buy Zend Studio for Eclipse PreferencesĪs with any major software product, you would expect to be able to have some sort of master control over its performance and look and behavior. Continue debugging as usual from here.Zend Studio for Eclipse Developer's Guide This will initiate a debug session on the Studio Client. The php parser location and the debug_host parameters above would probably be different. ![]() The command should be typed in one line, otherwise the QUERY_STRING environment variable will not affect php. This is done most conveniently in the following example: Make sure to set up the environment variable before as shown above. On the server machine, run the php-cli parser with the script you want to debug as a parameter. If you want to just debug a php script that reside on the local machine, where Studio client is running, either open the file in the editor or make sure it is included in the currently opened project.Use the server IP to point to the machine where PHP CLI will be running In Studio 5.x, go to Preferences -> Debug -> Debug Server URL.The following is not mandatory in some cases Make sure to fill the appropriate host name and port number above, according to the settings of the Studio clientĬheck the Studio client's preferences "Debug" tab for the "port" parameter Zend Studio Client configuration If you want the debugged script to be a local file, add the following string to the environment variable: " &no_remote=1"Įxternal links to setting Environment variables are at the end of this articleĢ. Setting Environment variables to act as Request parameters ![]() Edit "zend_debugger.allow_hosts" and add the IP address of the Studio client machine (e.g.: zend_debugger.allow_hosts=127.0.0.1/32,10.1.2.17/32). Configure in the php-cli' php.ini file to allow the client machine, upon which the Studio client is running, to perform debugging. ![]() You might also like to download the Zend Debugger standalone package from the Zend Studio downloads page and read the manual installation instructions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |