Ok, got it !
The problem is the following:
the mail is built using the following i18n pattern:
* content name
{0}
* site name
{4}
* content url {1}
* comment name {2}
* comment content {3}
but when the comment is pre-validated, the content url is taken from the "referer" header. This works fine on live (we are in direct) but not behind the front proxy...
and adding null as an i18n parameter does nothing so : {2} becomes {1}... and nobody becomes {4}
two ways for correcting this :
1) tranfering the referer header on proxy
2) adding an hidden field with the url in the comment form ; this solution may be a problem for those who have overriden the comment appearance (and I don't know if we can easily get it in a content xsl...)
Ok, got it !
The problem is the following:
{0}the mail is built using the following i18n pattern:
* content name
* site name
{4}* content url {1}
* comment name {2}
* comment content {3}
but when the comment is pre-validated, the content url is taken from the "referer" header. This works fine on live (we are in direct) but not behind the front proxy...
and adding null as an i18n parameter does nothing so : {2} becomes {1}... and nobody becomes {4}
two ways for correcting this :
1) tranfering the referer header on proxy
2) adding an hidden field with the url in the comment form ; this solution may be a problem for those who have overriden the comment appearance (and I don't know if we can easily get it in a content xsl...)