No spacing on support ticket text since 5.1

[DannyXYZ]

Hello,

i don´t know if this is only me, but since Version 5.1 the Text on the ticket messages have no more spaces if you logged in as client and look at the Ticket. So the text is all together and not good to read then. The Email versions seems to be fine.

In my case it look like this even if there are spaces between the lines:

don't know if this is a bug or any other problem. Tested it with my own and the original bootstrap template.

[Paul]

What version were you running before?

I'm pretty sure this is normal, a result of markdown only wrapping paragraph tags around only content and not white spaces.

[DannyXYZ]

Hello,

before i was on 5.0.4 now on 5.1.2. So at the moment, if threre is more text you can not read this text very good anymore.

The E-Mail versions are fine and look good, but if you view the ticket in Blesta, you can not read  the text as it all is line in line.

So for me all this looks like this:

[DannyXYZ]

On the logs i can see this notice, but i don´t know if this can have to do with this, but everytime i view a ticket,  this message is logged:

general.NOTICE: E_NOTICE: Trying to access array offset on value of type null {"code":8,"message":"Trying to access array offset on value of type null","file":"/vendors/blesta/parsedown/Parsedown.php","line":258} 

 

[Alk]

I have tested this on my install and it isn't just you.

You are correct that if you put a double space (I call them double lines) in a support ticket reply, the double lines are lost when the ticket is viewed in the client portal only. It is important to note that the double lines appear absolutely fine when viewing the ticket in the staff portal and as DannyXYZ has explained, it is fine on emails. So there is a discrepancy here with how the client portal is displaying the text.

As an aside, the "preview" button doesn't show what actually appears in practice for new lines either - this can throw you off, so best to ignore the preview and go by what you see.

 

 

 

[Alk]

On 7/23/2021 at 10:37 PM, DannyXYZ said:

On the logs i can see this notice, but i don´t know if this can have to do with this, but everytime i view a ticket,  this message is logged:

general.NOTICE: E_NOTICE: Trying to access array offset on value of type null {"code":8,"message":"Trying to access array offset on value of type null","file":"/vendors/blesta/parsedown/Parsedown.php","line":258} 

 

Regarding this error message that you see in your logs when viewing a ticket. I had already tracked down an exact matching error caused by the KB the other week, but I had not spotted that it was also appearing with support tickets. It is an error that is appearing under PHP 7.4, so I presume that you are running PHP 7.4 like me. It has taken me considerable time to finally put the information together such that I can post about the bug here - I've added in the error that you have observed when viewing tickets because I was also able to re-create it. I believe that the error from the support tickets is related to the error from the KB because they are the same/very similar and are all from the support manager plugin, so thanks for mentioning it, as I was able to combine it all into my one topic. I'm not a developer, but I can't see how these errors could be related to this particular problem with double line spacing not being displayed in the client portal, however.

[DannyXYZ]

yes right, i use PHP 7.4

i tested it now also with PHP 7.3. The message is also logged under 7.3 in my case.

[Jono]

To resolve, edit plugins/support_manager/views/default/css/styles.css and add:

.card .ticket-reply p {
    margin-bottom: 1rem;
}

 

[DannyXYZ]

if i had known it is just an css thing, i had fixed it my self.

Thank you for pointing this out. This works fine and it is solved now

[Alk]

Thank you Jono, I can also confirm that it is resolved with the fix that you have posted. The earlier screenshotted message from the client portal now appears correctly:

 

Will this fix now be making it into the CORE please?

[DannyXYZ]

it is already: https://dev.blesta.com/browse/CORE-4433

[Alk]

9 minutes ago, DannyXYZ said:

it is already: https://dev.blesta.com/browse/CORE-4433

Great. Thank you directing me to that.  Thank you again Jono.