By Romulo Provetti on Tuesday, 10 October 2017
Posted in General Issues
Replies 16
Likes 0
Views 1.5K
Votes 0
Hi. I have a problem. When we'll post a comment, back this error message:

SyntaxError: Unexpected token I in JSON at position 0

Can you help me?
Hey Romulo,

Are you planning to use https on the site or just http? Because there is one problem is because it is trying to use https on certain areas on your site.

By the way, can you please edit the post above and also include the FTP access?
·
Tuesday, 10 October 2017 22:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark. I don`t planins use https on the site now.
I included the ftp access in the post
Tanks
·
Wednesday, 11 October 2017 01:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Romulo,

I can't seem to replicate your issue(guest user: http://take.ms/sGliw, logged in user: http://take.ms/qGPGd).

Am I missing something here?
·
Wednesday, 11 October 2017 11:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi, Raymond. The problem seems intermittent. I did the test now and could not do it. See the error message.
·
Thursday, 12 October 2017 00:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Romulo,

Can you provide me the full url of the article? I have already tried this many times on many articles but I still could not replicate the issue.
·
Thursday, 12 October 2017 12:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello. I'm having the same problem again. Users can not post comments because they receive the message SyntaxError: Unexpected token I in JSON at position 0

When I clear the site cache it allows me to post the comments.

What can I do to fix this?
·
Wednesday, 24 October 2018 20:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Romulo,

I would like to test and investigate this on your site again, but the backend access no longer works(http://take.ms/PgnBU). Please advice.
·
Thursday, 25 October 2018 13:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Raymond.
I edited the post above and include the FTP and administrator access
·
Thursday, 25 October 2018 19:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Romulo,

Thanks for the access. You're right. Once I clear the cache, I can then comment without issue.

However, I cannot reproduce the issue again. Perhaps there is a certain kind of cache that is causing the error. Can you help me continue monitor this again and report to us once you experience the issue again?

Once the issue occurs again, remember to not clean the cache first. I would like to delete these cache one by one to find out which cache in particular is causing the issue(http://take.ms/r3dqq).
·
Friday, 26 October 2018 11:57
·
0 Likes
·
0 Votes
·
0 Comments
·
OK. I'll do this. Tks
·
Friday, 26 October 2018 20:36
·
0 Likes
·
0 Votes
·
0 Comments
·
You are most welcome, let us know if you still need any help on this.
·
Friday, 26 October 2018 22:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Romulo,

Thanks for the access. You're right. Once I clear the cache, I can then comment without issue.

However, I cannot reproduce the issue again. Perhaps there is a certain kind of cache that is causing the error. Can you help me continue monitor this again and report to us once you experience the issue again?

Once the issue occurs again, remember to not clean the cache first. I would like to delete these cache one by one to find out which cache in particular is causing the issue(http://take.ms/r3dqq).


Hi
The problem occurs now
I didn`d clean the cache
·
Wednesday, 28 November 2018 01:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Romulo,

It appears the cache system is caching the html content and token of the page and when you try to submit a new comment, the system detects that the token to submit this comment is no longer the same as the cached content and token, resulting in the error.

I would suggest that you disable Joomla cache for now(cache plugin and settings in global configuration), if not at least disable it on Joomla articles and perhaps consider using server side cache system like mod_pagespeed which does not compromise php performance.
·
Wednesday, 28 November 2018 14:12
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post