unable to publish webstories

@sudiksha152 Thank you for reaching out. We’ll be happy to assist.

Are you seeing any browser console errors from where the error appears? If any, please copy/paste the messages here or share a screenshot.

Can you confirm what your WordPress User Role is?

Hi,
this is the error showing in console.
web_stories_ga_tracking_id=UA-194044235-4&_locale=user 403

api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2 POST
wp-json/web-stories/v1/settings?web_stories_ga_tracking_id=UA-194044235-4&_locale=user 403

@sudiksha152 Thanks for sharing the console error. There are varying rights in the Web Stories plugin depending on your WordPress user role. Can you please tell us what your user role is?

Role is Administrator. But getting this error on editor role too.

Thanks

@sivagopi33 If you’d like to open a new support topic we’d be happy to assist with your case individually. Thank you!

@sudiksha152 To confirm, are you having issues with saving settings or issues with saving/publishing stories?

Were you trying to edit the Analytics field as an Administrator when that error message occurred?

A user with the Editor role will not be able to edit that setting as only Admins can update the google analytics ID for stories.

Hi
I’m facing the same issue even if I’m trying to update this as an Administration.
This issue is not solving.

@sudiksha152 Do you see any warnings or errors about REST API when checking your Site Health status (Tools > Site Health > Status)?

Hi.. getting this error in console

api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2          POST https://www.adda247.com/ml/wp-json/web-stories/v1/settings?web_stories_ga_tracking_id=UA-194044235-4&_locale=user 403
R @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
tryCatch @ wp-polyfill.min.js?ver=7.4.4:1
invoke @ wp-polyfill.min.js?ver=7.4.4:1
t.<computed> @ wp-polyfill.min.js?ver=7.4.4:1
n @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
u @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
H @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
p @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
H @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
p @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
t @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
Q @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
(anonymous) @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
F @ api-fetch.min.js?ver=b437dd9d1118e698b1b85961e759bf03:2
post @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:368
(anonymous) @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:370
(anonymous) @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:413
(anonymous) @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:409
l @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
p @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
(anonymous) @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
b @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
nt @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
et @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
rt @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
ct @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
P @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
Ma @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
Rc @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
zt @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
t.unstable_runWithPriority @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
eo @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
Ga @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
Lt @ stories-dashboard.js?ver=14a2a2226999ee45334095f19f071843:433
Show 20 more frames

There is no error regarding for REST API in tools> status.
only update for some plugin is mentioned there.

@sudiksha152 Thanks for checking.

1) Are you having issues with saving/publishing stories, or are you trying to update your Google Analytics settings?

2) Can you check if you get the same error in an incognito browsing window?

Hi,
I’m getting issue whenever trying to save Google Analytics Tracking ID. Same issue in incognito too.
Showing popup with message response is not a valid JSON response.

@sudiksha152 Some browsers have build in ad blockers, or there could be browser extensions active. Could you check if you have any active then try deactivating it to see if it helps?

If you like to provide your Site Health information I can check for any obvious plugin conflicts as well. You can share privately if you prefer.

https://pasteboard.co/0KeXMDkZVLKK.png
https://pasteboard.co/YCR4EcEdUosP.png

@sudiksha152 It appears you are using an older version 1.1.1 of the Web Stories plugin. There have been many updates, bug fixes, and enhancements since then so we recommend updating the plugin to version 1.19.0. Please let us know if the issue persists after updating the plugin.