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.