Installing on Windows

From ResourceSpace Documentation Wiki

Use the PHP automatic installer for best results. Select the extensions 'GD2', 'EXIF', 'SMTP' and 'MySQL'.

In the IIS administration tool (Control Panel -> Administration Tools -> Internet Information Services), under website properties you must add 'index.php' to the list of default documents under the 'Documents' tab.

When installing MySQL (again with the automatic installer) the 'simple' installation "Non-transactional Database Only (non-transactional MyISAM only)" is ideal for ResourceSpace.

Do not attempt to use CGI mode for PHP installation, as there are known issues with the CGI implementation in IIS such as dropped cookies causing log in issues.

When installing for IIS and using ISAPI for PHP integration (as opposed to CGI/FastCGI), in order for external tools (such as ImageMagick, FFMpeg) to work you must allow access to cmd.exe using the following on the command line:

cacls c:\windows\system32\cmd.exe /E /G IUSR_MYPC:F

Replace 'MYPC' with the name of your machine.

For IIS 5, in the web site properties in the IIS administration tool you must also change Application Protection to "Low (IIS Process)". For IIS 6+ you need to create a separate application pool for the ResourceSpace website, and then change the process identity from "Network Service" to "Local System".

When specifying paths in config.php you must avoid spaces as these cannot be correctly escaped. For example use the short form "C:\PROGRA~1" instead of "C:\PROGRAM FILES\".

For FFmpeg/ImageMagick etc. paths you may find you need to use forward slashes instead of backslashes.

If installing GhostScript (for PDF/EPS support), the current binary distributions use the name 'gswin32c.exe' when ResourceSpace is expecting to find 'gs.exe'. Renaming or copying the file will fix this issue.

WARNING: On Windows, PHP files must be modified with WordPad to ensure that the Byte Order Marker (BOM) is not prefixed to the file contents (e.g. [] or EF BB BF in hex). Notepad, in particular, should be avoided.

Files with a BOM cause PHP to display pages incorrectly. ResourceSpace demonstrates this problem by a) failing to render an image’s “preview” directly within the browser, and similarly b) spawning “download” images that cannot be opened in the browser.