[ZendTo] Feature Request custom string in subject per DropOff
Der PCFreak
mailinglists at pcfreak.de
Tue Jun 23 07:30:45 BST 2020
Hi,
wonderful!
Thank you Jules!
Peter
On 19/06/2020 18:22, Jules via ZendTo wrote:
> Folks,
>
> This feature is now in the latest beta release, 6.02-1 which is
> available from the beta page on the website at
> https://zend.to/beta
>
> When you create a new drop-off, the Subject line is shown next to the
> "From".
> *You can edit the Subject how you like.
>
> *The "EmailSubjectTag" from zendto.conf will still be added onto the
> start of the Subject before the emails are actually sent.
> If you would prefer that the EmailSubjectTag was included in the
> editable bit, so you can remove it, let me know.
>
> This has involved quite a major change in the HTML structure of the
> form, so if you see browsers where it doesn't display perfectly,
> please do tell me!
>
> Thanks!
> Jules.
>
> On 01/05/2019 10:03, Jules Field wrote:
>>
>>
>> On 30/04/2019 23:42, Kevin Miller via ZendTo wrote:
>>>
>>> I was thinking of something sort of along the lines of what Travis
>>> McDugald proposed:
>>>
>>> If (isset($messageID)) then $subject = [Zendto] . $messageID .
>>> $subject; else $subject = [Zendto] . $subject;
>>>
>>> although rather than an additional messageID I was envisioning just
>>> changing the prefix.
>>>
>> I am wary of allowing things like ticket numbers in the [] prefix, as
>> I bet some lousy ticketing systems out there will only spot the
>> ticket number if it has whitespace after it and not some bracket or
>> other punctuation.
>>
>>> I.e. I was thinking that [Zendto] would be a variable set in
>>> preferneces.php which could be customized. Something like:
>>>
>>> ‘Zendto_prefix’ => ‘[Zendto]’,
>>>
>>> which folks could simply change to what they wanted or leave it as
>>> the default. I didn’t really explain it very clearly.
>>>
>>> We’re probably the outlier, but the powers that be upstream of me
>>> decided we’d call our system “fileshare” rather than Zendto. So in
>>> my case I’d change the prefix itself if such was available. I can
>>> see the use case for what Travis, et. al. are proposing as well…
>>>
>> Greg has already answered that one for me. :-)
>>
>> Cheers,
>> Jules.
>>
>>> ...Kevin
>>>
>>> --
>>>
>>> Kevin Miller
>>>
>>> Network/email Administrator, CBJ MIS Dept.
>>>
>>> 155 South Seward Street
>>>
>>> Juneau, Alaska 99801
>>>
>>> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No:
>>> 307357
>>>
>>> *From:*ZendTo <zendto-bounces at zend.to> *On Behalf Of *Jules Field
>>> via ZendTo
>>> *Sent:* Tuesday, April 30, 2019 12:35 AM
>>> *To:* ZendTo Users <zendto at zend.to>
>>> *Cc:* Jules Field <Jules at Zend.To>; Kevin Miller
>>> <kevin.miller at juneau.org>
>>> *Subject:* Re: [ZendTo] [Feature Request custom string in subject
>>> per DropOff]
>>>
>>> Kevin,
>>>
>>> But in the case of a request, as much as possible is pre-filled for
>>> the customer dropping off files.
>>> All the other Subject lines generated are hard-coded (apart from
>>> translations).
>>>
>>> If you are thinking of either changing the [ZendTo] prefix to some
>>> other string, or adding something between the [ZendTo] prefix and
>>> the rest of the string, where and when is that going to be set?
>>>
>>> The "new dropoff" form needs to gain an extra "Message ID" (or
>>> whatever) box so people can put in their magic string.
>>>
>>> Are you saying the "send a request" form needs to gain it too?
>>> (And presumably if the answer to that is "yes", the "new dropoff"
>>> form would pre-fill the "Message ID" value from what was given in
>>> the request. And if that is the case, should the customer doing the
>>> dropoff be able to change the "Message ID" value at that point? I
>>> would suggest not.)
>>>
>>> I think we're all thinking about variations on either ticketing
>>> systems or people with multiple projects, where they need some magic
>>> value in the Subject line of *every* email message sent by ZendTo so
>>> that they can all be tracked and filed automatically.
>>>
>>> Cheers,
>>> Jules.
>>>
>>> On 29/04/2019 17:53, Kevin Miller via ZendTo wrote:
>>>
>>> Unless I’m misunderstand the conundrum, I’d say to let the
>>> requester enter the subject line, sans prefix, then prepend the
>>> system defined prefix at upload generation time. I.e., if I was
>>> requesting a dropoff I’d put in “My appropriate subject”. The
>>> person that is actually doing the dropoff would see that, and
>>> probably won’t think twice about it. Then, when the outgoing
>>> upload notification is actually complete, Zendto can prepend
>>> the system supplied prefix [Zendto] or [Whatever] and send
>>> that. I don’t think folks are in the habit of hand coding
>>> prefixes, so it’s unlikely one would end up with dual prefixes.
>>>
>>> Maybe there’s coding issues with that that make it difficult?
>>> Anyway, my tuppence worth…
>>>
>>> ...Kevin
>>>
>>> --
>>>
>>> Kevin Miller
>>>
>>> Network/email Administrator, CBJ MIS Dept.
>>>
>>> 155 South Seward Street
>>>
>>> Juneau, Alaska 99801
>>>
>>> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User
>>> No: 307357
>>>
>>> *From:*ZendTo <zendto-bounces at zend.to>
>>> <mailto:zendto-bounces at zend.to>*On Behalf Of *Jules Field via ZendTo
>>> *Sent:* Monday, April 29, 2019 6:19 AM
>>> *To:* ZendTo Users <zendto at zend.to> <mailto:zendto at zend.to>
>>> *Cc:* Jules Field <Jules at Zend.To> <mailto:Jules at Zend.To>
>>> *Subject:* Re: [ZendTo] [Feature Request custom string in
>>> subject per DropOff]
>>>
>>> Folks,
>>>
>>> I'm having a think about this one.
>>>
>>> The idea of the prefix is pretty simple, basically I would give
>>> you the "[ZendTo]" string (as an initial default value) in a
>>> "Subject" box in the new drop-off form.
>>>
>>> Whatever you end up putting in there gets used instead of
>>> [ZendTo] at the start of the email subject lines.
>>>
>>> However......
>>>
>>> If you request a drop-off, you get to supply the whole Subject
>>> line for the email to the person you want to send you their files.
>>> Ideally, that same Subject line would be used in all
>>> notifications etc about that drop-off.
>>> But they have entered the *whole* Subject line, not just the
>>> prefix to it.
>>> If I use their whole Subject line as a prefix, it's going to
>>> look weird.
>>>
>>> So what do I do for the Subject prefix, when it was created as a
>>> result of a request which had the entire Subject line supplied?
>>> I clearly can't ask the person sending the request to supply 2
>>> Subject entries — both the current whole Subject line *and* the
>>> prefix to use — as that would confuse the hell out of them.
>>>
>>> Any ideas please?
>>>
>>> Cheers,
>>> Jules.
>>>
>>> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>>>
>>> Hi Jules,
>>>
>>> yes it would be enough to allow 20 editable characters.
>>>
>>> via Smartphone
>>>
>>>
>>> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo
>>> <zendto at zend.to <mailto:zendto at zend.to>>:
>>>
>>> While no one has asked for this yet, I do see it’s
>>> usefulness.
>>>
>>> I do use custom strings in email subjects for some
>>> projects as well. Helps with sorting, searching, and
>>> filtering.
>>>
>>> Side note: great job on everything Jules, thank you.
>>>
>>> Sent from my iPad
>>>
>>>
>>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo
>>> <zendto at zend.to <mailto:zendto at zend.to>> wrote:
>>>
>>> Peter,
>>>
>>> You effectively just want to allow senders to
>>> customise the "[ZENDTO]" subject line tag in each
>>> drop-off, correct?
>>>
>>> Does anyone else need to do this too?
>>>
>>> Cheers,
>>> Jules.
>>>
>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>
>>> Hi Jules, hi all.
>>>
>>> I have a strange request from our ZendTo users.
>>> They asked if it would be possible to add a
>>> custom field when sending a DropOff
>>> that results in a custom text in all ZendTo
>>> email concerning this specific DropOff.
>>>
>>> Example current:
>>>
>>> [ZENDTO] One of the recipients has picked up
>>> your drop-off!
>>>
>>> Example requested:
>>>
>>> [ZENDTO] CUSTOM_STRING One of the recipients has
>>> picked up your drop-off!
>>>
>>> I asked a little bit about the purpose of their
>>> request and they told me that project teams sort
>>> their email by subject and
>>> consequently keep the project name
>>> (CUSTOM_STRING) in every subject of their emails
>>> concerning that specific project.
>>> So later they could sort by project name
>>> (CUSTOM_STRING) within Outlook to be able to
>>> verify when they sent a specific DropOff.
>>>
>>> Question:
>>> Is it possible to implement such a feature?
>>>
>>> I know that I could handcraft it but I don't
>>> want to make big changes to the source and
>>> always have to keep track of them when upgrading.
>>>
>>> I am currently not on the latest version of
>>> ZendTo, so if such a feature is maybe already
>>> present in the latest version, feel free
>>> to tell me.
>>>
>>> Thanks in advance.
>>>
>>> Peter
>>>
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to <mailto:ZendTo at zend.to>
>>> http://jul.es/mailman/listinfo/zendto
>>>
>>>
>>>
>>>
>>> Jules
>>>
>>>
>>>
>>> --
>>>
>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>
>>>
>>>
>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>
>>> action.' - Ian Fleming
>>>
>>>
>>>
>>> www.Zend.To <http://www.Zend.To>
>>>
>>> Twitter: @JulesFM
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to <mailto:ZendTo at zend.to>
>>> http://jul.es/mailman/listinfo/zendto
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to <mailto:ZendTo at zend.to>
>>> http://jul.es/mailman/listinfo/zendto
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> ZendTo mailing list
>>>
>>> ZendTo at zend.to <mailto:ZendTo at zend.to>
>>>
>>> http://jul.es/mailman/listinfo/zendto
>>>
>>>
>>>
>>>
>>> Jules
>>>
>>>
>>>
>>> --
>>>
>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>
>>>
>>>
>>> 'Find a place inside where there's joy, and the joy will burn out
>>>
>>> the pain.' - Joseph Campbell
>>>
>>>
>>>
>>> www.Zend.To <http://www.Zend.To>
>>>
>>> Twitter: @JulesFM
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> ZendTo mailing list
>>>
>>> ZendTo at zend.to <mailto:ZendTo at zend.to>
>>>
>>> http://jul.es/mailman/listinfo/zendto
>>>
>>>
>>>
>>> Jules
>>> --
>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>> 'Teach a man to reason, and he will think for a lifetime.' - Phil Plait
>>> www.Zend.To <http://www.Zend.To>
>>> Twitter: @JulesFM
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to
>>> http://jul.es/mailman/listinfo/zendto
>>
>> Jules
>>
>> --
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>
>> 'Making machines do what you want requires only two qualities:
>> 1) Being slightly more stubborn that the computer, &
>> 2) Remembering that computers are electrified rocks.' - @JediJeremy
>>
>> www.Zend.To
>> Twitter: @JulesFM
>
> Jules
>
> --
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'In Flanders fields the poppies blow
> Between the crosses, row on row,
> That mark our place: and in the sky
> The larks still bravely singing fly
> Scarce heard amid the guns below.
>
> We are the dead: Short days ago,
> We lived, felt dawn, saw sunset glow,
> Loved and were loved: and now we lie
> In Flanders fields!
>
> Take up our quarrel with the foe
> To you, from failing hands, we throw
> The torch: be yours to hold it high
> If ye break faith with us who die,
> We shall not sleep, though poppies grow
> In Flanders fields.' Lieutenant Colonel John McCrae
>
> Composed at the battlefront on May 3, 1915
> during the second battle of Ypres, Belgium
>
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200623/73303897/attachment-0001.html>
More information about the ZendTo
mailing list