Hi,
I just updated my version of Newspaper to the latest version and I’m trying to resolve some issues on the homepage, but changes within the tagdiv composer don’t save. I get two green notifications that the header and footer have saved, but the actual updates I make within each module on the page do not stick.
I’ve checked the console and I’m getting this 406 error on page load
/wp-json/td-composer/save_post?uuid=f7b8f47a-e938-4475-3089-1233c431c54d:1 Failed to load resource: the server responded with a status of 406 ()
and when I press save I get:
load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=5.8.3:2 POST /wp-json/td-composer/save_post?uuid=215d8094-a6a1-9ad7-e495-0cf282b5e3bc 406
I’ve gone through my plugins and deactivated basically everything non essential and the issue persists.
Can anyone provide any insights that could help?
Thanks
-
This topic was modified 4 years by
theulsterfry.
This is the third issue in a row that we are coming to this forum just to say, yes, we can confirm this issue also.
Hello!
Please make sure your account has an admin role and that all the requirements are done as you can see here: https://forum.tagdiv.com/requirements-for-newspaper/
We have a guide with some tips why our Composer is not working properly, please check: https://forum.tagdiv.com/tagdiv-composer-not-working/
If that problem is still there, then please execute these steps:
1. disable TagDiv Composer
2. uninstall(delete) TagDiv Composer
3. clear cache (if cache plugin exists)
4. install TagDiv Composer
5. activate TagDiv Composer
6. clear cache (if cache plugin exists)
Let me know the results!
Thank you!
Hi guys,
Thanks for your input. Just reporting back as I tried all of the above to no avail (sorry Bettinna) and so I escalated it to my hosting provider again (who had already ensured all php memory limits were met) as I suspected something else was underlying.
It turns out reason this wasn’t working was because it was triggering ‘mod_security’ rules within my hosting environment that were preventing the ajax calls from working. In short, these systems were blocking the calls to save_post, as it was being flagged as ‘XSS Attack Detected via libinjection’. They were thus able to whitelist the activity and now everything works as expected. There were two rules whitelisted I believe, one for page load and the other for save, which would correlate to the two 406 errors in my console log.
My hosting is a pretty standard linux setup, with widely available security features, and so others may have similar setup running on their host. Just sharing in case it helps others and/or tagdiv guys wanna include some caveats in your documentation.
The system is now working 100% fine and is really fast and powerful btw. I jumped from V8 of newspaper to this, and it’s quite the leap. Excellent work.