Messaging service Bug

Hi, I have a problem. When I send a private message to somebody the message does not take into account the layout, the spaces, the retreats in the line, the stakes in italic, bold etc. Impossible to edit, to delete the message. Impossible to create a new discussion with somebody, though I click it no matter. Any help? PS: English isn't my native langage, forgive me for mistake

Hi MJ , I'm sorry to hear that you're having issues with the site. Could you please carefully work through the first three steps of our guide to Solving Technical Issues ? Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome and Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable all add-ons/extensions and anti-virus programs. Step 3: Clear your cache If none of the above succeeds, please thoroughly work through Step 4 . (Don't forget the complete Console Log!) It would also help if you could post a picture or screenshot of these issues, if possible. Thank you!

Thanks for help. Well, sadly it doesn't work. So, Step 1: check! with Chrome, Firefox (and Edge), and it's the same issues. Step 2; check! I have enabled firewall, anti-virus, all extensions, trying with Chrome, Firefox, and Edge. Step 3: check! Step 4: in progress Operating System Windows Windows NT 10.0 Screen Resolution 1920 x 1080 Web Browser Chrome 51.0.2704.103 Browser Size 1920 x 955 IP Address  Color Depth 24 Javascript Yes Flash Version 22.0.-1 Cookies Yes User Agent Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Anti-virus software : Avast, Malwarebytes. Add-ons/extension blocked : Adblock Plus, Skype call, Avast SafePrice. Thanks in advance!

Thank you. A console log is a listing of the activity that Roll20 is doing while you play, so we can spot anything that deviates from the norm. Follow the instructions below to open your log, then just copy and paste everything into your bug report forum post in the Bug Reports section of the forums and we will aid you further. In Google Chrome Use the keyboard shortcut: Command - Option - J (Mac) or Control -Shift -J (Windows/Linux). If that doesn't work, follow these instructions: <a href="https://developers.google.com/chrome-developer-tools/docs/console#opening_the_console" rel="nofollow">https://developers.google.com/chrome-developer-tools/docs/console#opening_the_console</a> Could you please post two console logs? In each, try to capture one of the issues you're experiencing: Post formatting: open the console; write a small post with "spaces, retreats in the line, stakes in italic, bold etc."; submit the post; copy the log. Private message button: open the console; go to a user's profile; refresh the page; click on Send Private Message; copy the log.

Thanks a lot for rapidity! So, the console log indicates me this &nbsp;: 1-&nbsp;(index):818&nbsp;Uncaught SyntaxError: missing ) after argument list &nbsp; 2-&nbsp;romain-medan:604 Uncaught SyntaxError: missing ) after argument list v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 614, left: 111, width: 263, height: 40} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 614, left: 111, width: 263, height: 40} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 455, left: 622.875, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 455, left: 622.875, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 696.3125, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 696.3125, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 769.75, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 769.75, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 916.625, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 916.625, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 990.0625, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 990.0625, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 1063.5, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 1063.5, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 622.875, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 622.875, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 769.75, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 769.75, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 990.0625, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 990.0625, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 1136.9375, width: 64, height: 64} browse.js?1452029248:32 autograv v2.js?1468423133:10 SHOW TIPSY v2.js?1468423133:10 SHOWING v2.js?1468423133:10 Object {top: 391, left: 1136.9375, width: 64, height: 64} browse.js?1452029248:32 autograv Thanks

Thank you. A Dev will drop by and take a look.

Thanks a lot!

Hey MJ, sorry you're having issues with the private messages. Can you send me a private message me the link to the PM that isn't working so I can take a look at it and see if I can figure out what the issue is. I think it might be an issue with the special characters, which is why it's not working correctly for you but when I do it in just English it works fine. It's causing the JavaScript to break, which is why you aren't able to edit/delete/anything to that message in particular.

Well, unfortunaly I can't send you a private message. It's doesn't work beside I try with different system (Chrome, Firefox and Edge). Always the same console logs information:&nbsp;phil-b:622 Uncaught SyntaxError: missing ) after argument list I note your suggestion about special characters, in fact actually I use accent, but before even in french I haven't any problem on Roll20 and actually on other forum or plateform, like this one. Just with this private message system.

I'm sorry, I misunderstood, I though just a single chat was broken for you, not all of PM system. I did some poking around, and it's specifically because of some characters added in the French translation of that page that are breaking the JavaScript. It is an easy fix, and I will go ahead and fix that now, but it probably won't go live until tomorrow. If you need to use the PMs before then, you can temporarily switch your account language to English and everything should work just fine.