Response Time
24 — 48 hours
My main question is: can I increase or remove the timeout for creating a blog post?
I have verified an issue on my production, test, and StackIdeas Demo sites.
If you create a new blog post, after a certain amount of idle time the post will be unable to publish or save as draft. When the issue happens, after trying to save the post status returns "JSON.parse: unexpected character at line 1 column 1 of the JSON data". In my tests, I begin to see the timeout error after waiting 20 minutes.
Here's why this is a problem for my site: I have a lot of users who will make posts and do research at the same time, usually in another browser tab. It frequently takes them longer than 20 minutes to compose their blog post. It gets frustrating to them because the composer keeps working and letting them build the post even past 20 minutes, but then they lose all of their work because it will not save or publish.
Now, sometimes I can recover it using the backend and finding an entry under Posts -> Drafts labeled "Initial Post (Revision #1)", but I still lose a lot of content from the timeout.
To recreate this issue: Create a blog post, choose any template, enter a title and some text in the body, and then just open a new browser tab and leave the post tab alone for 20 minutes. Come back after 20 minutes and try to save or publish the post, you should get the error "JSON.parse: unexpected character at line 1 column 1 of the JSON data" or similar.
Thank you for any help you can provide!
P.S. My production site is run as an internal-only intranet for a company, so I cannot easily provide access. As I mentioned above, I can recreate this error on your demo site, so you shouldn't need access to my site in order to troubleshoot, and I should be able to apply any fixes to my site myself. If you do need access to my site, I can make some configuration changes and allow it, but will take 24-48 business hours (M-F).
P.P.S. For the same reason that my site is hosted internal-only, I have not assigned a domain to my products and I hope this is not an issue.
I have verified an issue on my production, test, and StackIdeas Demo sites.
If you create a new blog post, after a certain amount of idle time the post will be unable to publish or save as draft. When the issue happens, after trying to save the post status returns "JSON.parse: unexpected character at line 1 column 1 of the JSON data". In my tests, I begin to see the timeout error after waiting 20 minutes.
Here's why this is a problem for my site: I have a lot of users who will make posts and do research at the same time, usually in another browser tab. It frequently takes them longer than 20 minutes to compose their blog post. It gets frustrating to them because the composer keeps working and letting them build the post even past 20 minutes, but then they lose all of their work because it will not save or publish.
Now, sometimes I can recover it using the backend and finding an entry under Posts -> Drafts labeled "Initial Post (Revision #1)", but I still lose a lot of content from the timeout.
To recreate this issue: Create a blog post, choose any template, enter a title and some text in the body, and then just open a new browser tab and leave the post tab alone for 20 minutes. Come back after 20 minutes and try to save or publish the post, you should get the error "JSON.parse: unexpected character at line 1 column 1 of the JSON data" or similar.
Thank you for any help you can provide!
P.S. My production site is run as an internal-only intranet for a company, so I cannot easily provide access. As I mentioned above, I can recreate this error on your demo site, so you shouldn't need access to my site in order to troubleshoot, and I should be able to apply any fixes to my site myself. If you do need access to my site, I can make some configuration changes and allow it, but will take 24-48 business hours (M-F).
P.P.S. For the same reason that my site is hosted internal-only, I have not assigned a domain to my products and I hope this is not an issue.
9 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
