Our apologies for the delay in completing this enhancement. We have now updated the size of the thank-you email subject field to store up to 100 characters. BTW, this limit only affects the number of chars you literally type into the thank-you Email Subject field; template substitution variables such as [%item_name%] can still expand the as-sent Subject line beyond 100 chars, so long as the un-substituted variable codes themselves and the rest of the subject text all fits within 100 chars. As soon as Robin gets his laptop back from the shop, we will be able to update the product config input field to restrict the number of characters you can type in that field accordingly.



FWIW, that ongoing laptop repair is a significant reason the "next planned incremental update" to E-junkie's codebase (which would have included this email subject enhancement) had been delayed, as all of Robin's dev software is installed on that lappy, and what was supposed to be a simple cooling-fan replacement with an ETR of less than a week has been dragged out for nearly a month by now (due mainly to HP sending the wrong parts!). Thanks for your patience and understanding.

As announced above last week, we have implemented the extension of the email subject line that you requested, which now accommodates up to 100 characters as-typed into the Email Subject field of your Seller Admin product configs.



As for the Email Message body, we have no set limit, but the Admin screen does tend to gag on text input of more than 100kB or so; if you really need to send more text than that -- frankly, I've never even seen any real-world email message anywhere near that big that didn't have a file attachment -- we'd recommend doing so as either a File Download for that product or just provide a link in the email to a page on your site which has that boilerplate text on the page.

I'd be glad to respond, if only to say "I don't know" and perhaps speculate that it may have something to do with the parentheses around the substitution variable code? Have you tried it without parens, or with a [space] character between the parens and the variable code? Robin may have a more definitive answer to chip in here...



As for the email subject-line size, you can already type or paste up to 100 characters in there. Like any text-entry box where the field/buffer size exceeds the visible box size, the box contents just scroll to show whatever will fit within its width at a time, but everything you type is still in there even when you can't see it all at once.



You had never mentioned anything about increasing the actual message-body length in your earlier requests, but that is a hard technical limitation we cannot easily just remove or increase, since we are not arbitrarily limiting that field with any deliberate setting that we could just modify. Perhaps Flash won't take more than ~100k of user input, or perhaps it can't pass that much data to our backend, or perhaps there's something else entirely going on, but it may not be something we have any control over (if it's a Flash or interoperability limitation), and it's never been an issue for anyone until you brought it up and we discovered it was gagging around the 100k mark.

I'll leave the subject line substitution issue to Robin's superior expertise...



For the message body, sorry, I should have typed 100kB, as in 100,000 Bytes. We haven't identified an ~exact~ number of characters it will tolerate, just noticed that strange things start happening when the raw data going into that field gets near the 100kB mark. If you can save your message text in a Notepad .txt file, and if the resulting file size weighs less than 100kB (and the further below that mark, the better), then you should be fine pasting that text into the message body field.

lemonbar([%payer_email%])



I tried putting this in the email subject line and it didnt replace the code. it just put that text.



What went wrong?

There is no reason for it to work. The only template variable for the subject is [%item_name%] and we don't mention otherwise anywhere.