The updated php.ini was stored in %UserProfile%\AppData\Local\VirtualStore\Windows\php.ini.
#HOW TO INSTALL PHP 5.2 ON IIS 7 WINDOWS 7#
Where Vista wouldn’t let me edit this file at all, Windows 7 happily lets me modify it but transparently saves the changes in a different location. The problem was caused by something called the Virtual Store, an application compatibility feature that existed in Windows Vista but works a little bit differently in Windows 7. But even after restarting IIS my configuration changes never took effect. Windows 7 was more than happy to allow me to modify and save this file in the same location, logged in with the same credentials. On Windows Vista I simply wasn’t allowed to edit files under the \Windows directory (specifically php.ini) when logged in as a Standard User. The Problem : Editing php.ini as a Standard Userĭuring the process of installing PHP on Windows 7 you will be required to copy php.ini into the C:\Windows directory, and later point you’ll most likely need to edit this file to suit your needs. However there was one quirky difference between installing PHP on Vista and installing PHP on IIS 7 that developers may want to be aware of before they follow my lead.
#HOW TO INSTALL PHP 5.2 ON IIS 7 HOW TO#
There are plenty of other quality tutorials out there explaining how to get PHP working on IIS 7 so I won’t bother beating that particular dead horse. My development stack consists of Netbeans IDE, PHP 5.2.8, and IIS 7.
Last week I decided to take the plunge and install the release candidate of Windows 7 on my office workstation where I happen to do a lot of web development and testing.
0 kommentar(er)
