I’m not able to reproduce this on the latest version (5.0.0 RC-7) - it is possible that we have fixed an issue related to this for 5.0.
We are releasing v5.0 today, so I’m wondering if you’d like to upgrade after it is available. You can also first test on our nightly build server which will be on v5.0 final version in a few hours.
I am now on 5.1.0 and still seeing the same behaviour. I did check your nightly build server which displays the post correctly. (We will upgrade to 5.2 soon but I really do not think that is going to change anything since I have seen this across multiple versions already).
So I think it must depend on something in the database configuration. Any help in figuring this out would be very much appreciated…
Thanks @amy.blais. Do you know what they did differently to our (unsuccessful) attempts to reproduce on the test server? The ticket doesn’t explain the difference and I wonder if it points to a workaround.
@gubbins I just tested this on a few other testing servers we have and I’m not able to reproduce this in different places, so I’m guessing it might have something to do with a specific environment - I’ll ask my colleague more details on the environment he has.
@gubbins - We are both on the same environment (desktop app v4.1.2, Mac OS 10.13.6, pre-release) so it doesn’t seem to be the environment after all - I’ll see what the devs find when they investigate a fix for this.