Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI've just posted the code..hope that helps. The problem is...even the links have white spaces and it is converted to "+" sign and that broke the links . The white space is in HTML source as well. Unfortunately, I can't share the email, coz it is a private emails...Again this happens randomly. So frustating...
      singulars
    2. COIf it were me, I'd add code to save the body text to a temporary log file every time a message is sent (along with any date/time stamp, subject, etc. you need to identify that message from another). Then every time the mysterious space appeared, I'd compare the corresponding log file entry to that message. That would at least let you figure out whether your script is doing it or it's "out it the ether". Chances are, of course, that your script is inserting the spaces. But then you'd have a place to play with trying different approaches (the log file).
      singulars
    3. COSome stuff to try... Try using single quotes when you don't need variable interpolation. Instead of building up the string in parts in that function, put the message-building into a function of its own, with the fill-in values put as parameters, and returning one big message string. Then, of course, unit test the hell out of that message-building function :) (Personally I like to create message template files like "Dear [Name], Thanks for buying [Product] etc", and then have a generic function that reads the files and does substitutions - that way you can change the message w/o editing code)
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload