Support Ticket Answer Have Randon Sentence In Bold

[serge]

Sometime when I answer a support ticket, I can see when checking the sent answer, some sentence passed in bold.

 

I mostlly create draft response in a text editor that do not have formating feature, I use Gedit, and it's help me to check the spelling, and after that I do cut and paste in blesta support ticket answer.

 

 

[Michael]

Are you using ** or * next to words? That might be why as it's markdown.

[serge]

 Posted Today, 09:43 AM

Are you using ** or * next to words? That might be why as it's markdown.

No ** or * used

[Michael]

 Posted Today, 09:43 AMt

Are you using ** or * next to words? That might be why as it's markdown.

No ** or * used

 

 

Or was it in the client reply if it's that it might be bold text used or they did ** or * to make it go bold.

[serge]

it's only happen in our support reply, it's do not come from customer side

[Michael]

it's only happen in our support reply, it's do not come from customer side

 

Not sure then, but here's the markdown commands: https://help.github.com/articles/markdown-basics/

[serge]

Thanks for info, no such characters was used in our reply.

 

I think I should post a feature request for we have a button to open a windown where to paste text content we want to add in the suport ticket, some other software have this to prevent such kind of issue I had.

[Tyson]

Can you provide an example of content you've added that resulted in bold text? You could have added two underscores to make it bold, or an email client can do so as well.

[serge]

I'm doing PM to you with full content

[PauloV]

I have detected the problem and implementos a fix on my support manager pro (its a core file)

Try to write this in the Ticket below eheh :
 

Im
-
Bold
--
Or not?

The problem is on markdown , here is the solution

 

[blesta-instalation-directory]/vendors/parsedown/Parsedown.php

 

find on line 608:

return $Block;

 

replace (comment that line) with:

 

//return $Block;

And that's it

Edited August 25, 2015 by PauloV

[Michael]

I have detected the problem and implementos a fix on my support manager pro (its a core file)

Try to write this in the Ticket below eheh :

Im

-

Bold

--

Or not?

 

Nice find never would have thought of that, - normally do a HR.

[PauloV]

Nice find never would have thought of that, - normally do a HR.

 

 

I have now posted the solution above

[serge]

Thank for investigation,

 

by the way I use Blesta native support manager

[Michael]

Thank for investigation,

 

by the way I use Blesta native support manager

 

Yeah the fix works on both as it's the core vendors file.

[Tyson]

I haven't looked at the code. What does commenting out the return line intend to solve?

[Tyson]

The OP's issue ended up being caused by normal markdown behavior in the creation of a header (<h2>) tag. The header font was larger and appeared bold.

 

e.g.

He had a sentence on one line immeditaelly followed by a line of hyphens:

This sentence was translated to a header <h2> in markdown.
----------------------------

when the desired behavior was a paragraph followed by a horizontal rule, which requires a blank new line in between, e.g.

This sentence becomes its own paragraph <p> when it is followed by a blank new line.

----------------------------