The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.1.31 (Linux)
|
Different path display in email to form owner as opposed to the sender - Printable Version +- Form Tools (https://forums.formtools.org) +-- Forum: Form Tools (https://forums.formtools.org/forumdisplay.php?fid=1) +--- Forum: General Discussion (https://forums.formtools.org/forumdisplay.php?fid=5) +--- Thread: Different path display in email to form owner as opposed to the sender (/showthread.php?tid=1665) |
Different path display in email to form owner as opposed to the sender - filch - Sep 29th, 2011 Ben, Why is the path to an uploaded file showed differently in the email sent to the client or form owner than it is in the users email? In the one sent to the client, the path to the file is hidden and just shows the link as the filename. In the email sent to the sender, it shows the complete path from root to the file ... which I really do not want to show? Dave RE: Different path display in email to form owner as opposed to the sender - Ben - Sep 29th, 2011 Hi Dave, That sounds like a bug... could you post your email template here? (just the appropriate bit, if it contains sensitive information) - Ben RE: Different path display in email to form owner as opposed to the sender - filch - Sep 30th, 2011 (Sep 29th, 2011, 8:12 PM)Ben Wrote: Hi Dave, Here's the HTML portion of the email sent to the poster: Code: <p> and the text only version: Code: Thanks for your submission to the Community Service Awards! Below is what you submitted. If there are any errors or ommissions, simply reply to this email with your changes. Dave RE: Different path display in email to form owner as opposed to the sender - Ben - Oct 2nd, 2011 Hi Dave, I think it's just this bit in your HTML template: ({$field.folder_path}). Just delete that, and the path will disappear. It shouldn't be there: it looks like it's some old debugging code that snuck in there. I'll remove it in the next version of the Core. Thanks for letting me know! And sorry for the bug. - Ben |