Noteworthy changes

  • Zend Framework 2 updated to version 2.4.2
  • Apigility 1.1 is now used in project templates
  • PHP 5.6 binaries are update to version 5.6.7
  • Max memory heap size is set back to 1 GB for 32-bit installations
  • Fixed issue with invoking Encode Project on Mac
  • Fixed issue with mobile apps on Windows when the Android SDK is installed on a location containing spaces in the path
  • Added error dialog with description of possible reasons that may cause problems while trying to read info from PHP executable (eg. incompatible version of Microsoft Visual C++ Redistributable on Windows)
  • Added reporting of problems related to setting up a valid port in debugger connection settings (eg. warning is reported if given port is already in use)
  • Improved 'Dark' theme presentation model of wizards & dialogs for creating/editing PHP servers and executables
  • Fixed issue with deploying applications to Zend Server on nginx
  • Fixed issue with saving URL filters for Zend Server monitoring
  • Fixed issue with saving URL filters for Zend Server debug mode
  • Fixed issue with failing test for Zend Debugger connection when 'Use SSL encryption' option was turned on
  • Fixed issue that was causing wrong debug port to be set (10000 instead of 10137) for Zend Debugger in newly created PHP servers & executables
  • Fixed issue with unsupported 'Source Location' option for XDebug launch configurations
  • Fixed issue with NPE occurring when trying to open a PHP file from code trace editor
  • Improved content assist performance for projects with large number of types
  • Fixed issue with Zend Studio freezing after hyperlinking just after Zend Studio start
  • Minor fixes for content assist

System Requirements

  • Supported Operating Systems:
    • Windows 7, Windows 8
    • Linux x86, Linux x86-64
    • OS X 10.10 Yosemite
  • 1.5GHz processor
  • 2GB RAM
  • 1GB of hard disk space

PHP 5.5 and 5.6 built-in executables (Windows only)

  • The PHP 5.5 and 5.6 built-in executables require the Visual C++ Redistributable for Visual Studio 2012 (x86 variant) to be installed in the operating system. The MSI installer of Zend Studio 12.5 and later installs it automatically, but users upgrading from earlier Zend Studio version must install it manually from here: http://www.microsoft.com/en-us/download/details.aspx?id=30679

Apigility integration requirements

  • Internet Explorer >=10 is required on Windows for the Apigility Editor to render correctly.

Mobile development requirements

Code Trace requirements

  • Flash Player must be installed in the operating system.

Known Issues

  • CordovaSim requires manual configuration of JRE (Mac OS X only). For some reason the Eclipse Platform on Mac OS X does not automatically configure the JRE that runs Studio. Users must manually configure it in the Java > Installed JREs preference page.

  • Reset Perspective may be required after installation of the Terminal plugin. This is required in case it does not appear in the Show In context menu.

  • During update of Studio a security warning about unsigned content may be shown. You can safely ignore this warning and proceed with the upgrade.

  • Z-Ray may not render correctly inside Zend Studio on Windows. A workaround can be applied in one of the following alternative ways:

    • Modify Zend Server configuration to include the "X-UA-Compatible: IE=edge" HTTP header in the response. If Zend Server is running on Apache HTTP Server then:
      • Add the following line in the httpd.conf file:

        Header add X-UA-Compatible "IE=edge"
        
      • Restart the Apache HTTP Server.

      • Reopen the web browser inside Zend Studio.

    • Modify the application to include "X-UA-Compatible: IE=edge" HTTP header in the response:
      • Add the following line in a suitable place in your PHP code:

        header("X-UA-Compatible: IE=edge");
        
      • Reopen the web browser inside Zend Studio.

  In Zend Server 8 and later Z-Ray will automatically add the "X-UA-Compatible: IE=edge" HTTP header in the response, so the above workaround will not be required.