Hello,

we have a makro running, which is preparing the answers from our customers into a special excel file.

This makro worked great until we moved from 2.05+ to 3.17+.

This makro is looking for a token on the 5th position of the answer mail from our customer.

Now the token entry moved to 6th position and of course this makro is not finding the token on the position where it was.

On the 5th position there is now a new column called seed or Zufallsgeneratorwert.

My question ist how to get rid of this entry in the mail , without changing the makro, because I don't need it?

See attachments please!

Many thanks as always

Haydar

What kind of email are you referring to? If this is a standard mail that comes directly from Limesurvey, it is for sure easier change the macro to read the 6st column instead of the 5th, rather than going into the source code to change the content of this email.

I guess this is the admin notification email and the information in the email is generated by {ANSWERTABLE}. So you can't exclude this individually and the seed is generated per default, I don't think there is no way to exclude the seed without hacking the code.

I am quite sure that changing the macro will be a lot easier than hacking Limesurvey. and there is always the risk that this hack is overwritten by updates.

Thanks,

and where I can find this "Answertable"????

I don't know where this is in the source code. {ANSWERTABLE} is just a placeholder like {TOKEN} or {QUESTIONCODE}. Somewhere in the source code this needs to be translated into the output it generates. Where this would be? I don't know. You will have to search the source code.

Maybe you find it here on github, searching for {ANSWERTABLE}:
github.com/LimeSurvey/LimeSurvey/search?..._q=%7Banswertable%7D

Plugin start point : gitlab.com/SondagesPro/mailing/adminNoti...nHtmlAnswerTable.php

Hello and many thanks.

but I would like to know, where the part with "seed" definition is, so I can remove or deactivate it, so the token entry is on the 5. Position again as it was.

many thanks as always

Haydar