Email config

[weezer316]

Hi

Just a quick question! I am trying to tailor the notification and subscription message but I am having all sorts of probelms!

if I remove all the subscription.subject.x data from the OpenKM.cfg file, they arrive fine and shwoing the correct data. However, If I try and add my own settings there, all i get in place of the variables when the email arrives is {0} or {1} etc!

Im absolutely certain it isnt my config as copying the ones of the documentation website prodeuces the same results!

Any Ideas? Can someone post their subscription and notigy config parameters?

Wheeler

[jllort]

First which is your OpenKM version, because in last release we've make some changes in OpenKM.cfg declaration.

Second put your property and what you receive and we'll take a look.

[weezer316]

Its version 4.1. I am using. the latest i believe.

The properties I have been setting for the subscription and notification are currently what is on the openkm website, under faqs. For the record, here they are:

subscription.message.subject=OpenKM - {0} - {1};
subscription.message.body=<b>Document: </b><a href=\"{0}\">{1}</a><br/><b>User: </b>{3}<br/><b>Event: </b>{4}<br/>

notify.message.subject=OpenKM - NOTIFICATION - {0};
notify.message.body=<b>Document: </b><a href=\"{0}\">{1}</a><br/><b>User: </b>{3}<br/><b>Message: </b>{4}<br/>


Both emails I recieve dont have the variable information, just the numbers. So the subscription email I receive is like below, when the pathname and user etc should be in place of the numbers.

Document: {1}
User: {3}
Event: {4}


Like I said, this is off the openkm website, http://www.openkm.com/FAQ.html. Thast why im certain my settings were not what is causing it as they were giving the same thing.

[weezer316]

Ignore me! Got it! Just realised 4.1 is different. Found the config here: http://wiki.openkm.com/index.php/Notifi ... n_messages

My apologies for wasting your time! Many thanks

Wheeler

[jllort]

Don't worry as I supposed you was not informed in configuration changes occured at version 4.1 in mail messaging configuration params.