Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,348
Community Members
 
Community Events
176
Community Groups

I cannot post answers in the community

As soon as I post one answer (the first always works fine), the following answers will not work as I always get the following script's error in the console:

 

Uncaught SyntaxError: Unexpected token h in JSON at position 149
at Object.parse (<anonymous>)
at Function.parseJSON (lia-scripts-common-min.js:32)
at Object.success (thread-reply-field.min.js?sha=2814745:2)
at fire (lia-scripts-common-min.js:55)
at Object.fireWith [as resolveWith] (lia-scripts-common-min.js:60)
at done (lia-scripts-common-min.js:494)
at XMLHttpRequest.callback (lia-scripts-common-min.js:547)
at XMLHttpRequest.nrWrapper (1308564:3)

 

I have tested on Chrome and Safari, used different sessions and the result is always the same. Even if I logout and login again it is not working. Except from the console, nothing is showed to explain the error.

2 answers

0 votes
Shannon S Atlassian Team Jul 16, 2020

Hi Hugo,

Can you confirm with what Matthias said, if you're still having the issue today, and only yesterday? What is the exact behavior in your browser UI when this occurs?

Secondly, Are you having difficulty answering any questions at all, or only specific ones? Does this happen no matter which device you use (another computer, phone, etc.)?

Thank you!

Shannon

It seems to be only specific ones, as you can see I can post here with no problem.

I'll do it while capturing the exact behavior.

I did not try with my phone yet, neither with another computer.

You can see the exact behavior in my Chrome Browser on Catalina, here: https://1drv.ms/v/s!At92Fo0U3hMBjfM14HQEry3DOeeWNg?e=ApuNme

Shannon S Atlassian Team Jul 17, 2020

Hi Hugo, 

Thank you for sharing that video. It's very helpful!

In this case, you're replying to an answer, so it might not trigger the same behavior. If you were to reply instead in the Suggest an answer field, does the issue occur?

Shannon

Hi Shannon, yes it occurs... in the following video capture I was able to replicate the strange behavior:

  1. I try posting an answer here
  2. The first Suggest an answer was posted successfully
  3. The second Suggest an answer generate the same error that I warned you about
  4. From now on, no matter what other browser or session I use (obviously connecting with the same account as here), the error will also occurs
  5. That is not exactly true, I was able to post two more "test" in my Safari before the problem occurred again...

 

You can find the video here (with real life sounds behind hihi).

Shannon S Atlassian Team Jul 21, 2020

Hi Hugo,

Thank you for sharing that. The team has been looking into this, and so I'll share your most recent example with them now. I'll let you know if I find out anything about this issue.

Take care,

Shannon

Shannon S Atlassian Team Jul 22, 2020

Hugo,

We believe we found the cause of this, and we're now working on a fix. I'll update you when that's completed!

Shannon

Like Hugo likes this

Great job, thanks!

Like Shannon S likes this
0 votes

Hi @Hugo

There was an error in the community yesterday that answers were not showing for a lot of posts. Did you experience this issue only yesterday? Or already in the weeks before?

Cheers,
Matthias.

Yesterday and before, I'm trying again now.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events