Sitemap Generator Forum

We are having trouble updating the .conf file through index.php.  All fields are updated on http://<sitename>/generator/index.php page, clicking 'save' clocks/spins for several minutes then results in

Current Config:
Windows Server 2008 R2
IIS 7.5
PHP 5.3.19

All permissions are set on ror.xml, sitemap.xml, and the /data directory. 
We have attempted to run on PHP 5.4, uploaded the latest generator version, and have changed memory, max_execution_time, etc within PHP options but 'save' continues to spin.

The attached server php logs show several php errors, notably:
Failed to write session data (files). Please verify that the current setting of session.save_path is correct (C:\inetpub\IowaHealth\generator/data/) in Unknown on line 0

generator.conf is created when index.php is launched initially but no changes are applied at 'save'

Any assistance would be appreciated.
Thanks!

Hello,

Since your site is hosted on windows platform, in order to complete installation you should also set file permissions accordingly (allow write access to sitemap.xml, ror.xml files and data/ folder). On windows servers this is done in hosting control panel or via remote desktop access (instead of FTP).
 

We have set permissions for these directories.  Logged in via RDP, gave IIS users and Everyone full access to sitemap.xml, ror.xml, and the generator\data directory.

-any other ideas? 

generator.conf is created within the data dir when index.php is originally launched but does not change when 'save' is clicked. 
No warnings about permissions are shown when index is launched and configuration checker runs. 

Please try to also allow write access for generator.conf file in data/ folder.

yes, write acccess to generator.conf is set. 
-opened for 'everyone' group to have full access to generator.conf, the generator/data, sitemap.xml, and ror.xml and still see the site spin at save. 

Has anyone seen this work with IIS 7.5 running on Windows Server 2008 R2?  We have tried the latest PHP version as well as 5.3. 

Any other suggestions would be appreciated.

Thanks!

Hello,

it should be allowed for specific user running IIS (it might be IUSR_*) - allowing for Everyone group is not sufficient.