PHP support includes:
- Possibility to create PHP files and classes from templates.
- Full PHP 5.4 syntax support.
- Syntax highlighting.
- Error highlighting.
- Basic on-the-fly code completion.
Resolution of include statements and file references, including references to PHAR archives.
All the PHAR files from the current project and the specified include path are shown in the project tool window under the Project View/Libraries/PHAR node and available for browsing right there.
- Class Completion.
- Intention actions and quick fixes.
- Surrounding with code constructs and or or .
- Code inspections.
- Jump to declaration (, or , or , or , or , , or , or , , , or , or or , or , or or ).
This part describes some procedures that are specific for developing PHP applications and some preliminary steps that are required to configure PHP development environment.
Follow these general steps:
- Configure the PHP development environment.
- Enable PHP support in IntelliJ IDEA.
Start creating a project from scratch. On the first page
of the New Project wizard, select Static Web.
To run and debug your application on a local Web server, create the project root below the Web server document root. Thus your application sources will be "visible" for the local Web server.
- Create and configure the required data sources.
- Populate the application using provided coding assistance.
Deploy the application.
With IntelliJ IDEA, you can flexibly configure deployment of PHP applications. For example, you can set up your PHP project on a local Web server from the very beginning, or develop and test an application locally and then upload it to a remote Web server, etc.
Run the application. You can do it in several ways:
- From IntelliJ IDEA using a run configuration of the type PHP Web Application to view application output in a browser.
- From IntelliJ IDEA using a PHP Console run configuration to view the application output in the Run tool window.
- From IntelliJ IDEA, using a built-in Web server. This approach saves your time and effort because you do not need to deploy the application sources.
The following optional steps may be helpful: