Details lacking regarding details of IIS support (or locak thereof)
I noticed the mention "Plugin not consider the IIS. Sorry. We are waiting patches for IIS." in the description/README of this plugin. Could you provide more information about this and what could help solve this? Is there a technical blocker for this to be implemented or simply not a priority? Is this a server or client limitation (or other problem)?
This would be useful for contributors considering helping with this and in general for people interested in having ClickHeat working for their IIS visitors/users.
Thank you for using the ClickHeat. And Sorry for this plugin is not enough for you.
Directory piwik/plugins prohibits execution condition resolution in the standard setting. So I put authority .htaccess in piwik/plugins/ClickHeat to excecute piwik/plugins/ClickHeat/ClickHeat.php. But this way - quick-and-dirty work. For IIS should put a special xml file as .htaccess, but I could not solve this problem. Because I do not know this xml format. But if I use the routines in piwik/plugins/Installation/ServerFilesGenerator.php, I will be able to solve immediately, because the routines make .htaccess and xml for IIS from one root of the script PHP. This is not a quick-and-dirty work, I want to use this method.
And I know, there is case-sensitive issues for IIS, but now I spend time to make a non-stop Piwik, when the data base stopped to upgrade Piwik.
How can I help to add IIS support?
web.config for IIS
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="ClickHeatRequestBlockingRule" enabled="true" stopProcessing="true">
<match url=".*" />
<conditions>
<add input="{REQUEST_FILENAME}" matchType="Pattern" pattern="(click\.php|.*\.(gif|ico|jpg|png|svg|js|css|htm|html|swf|mp3|mp4|wav|ogg|avi))$" ignoreCase="true" negate="true" />
</conditions>
<action type="CustomResponse" statusCode="404" statusReason="File or directory not found." statusDescription="The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable." />
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>