Closed stevegrunwell closed 6 years ago
This appears not to be a conflict or memory issue, but rather an issue with invalid markup being returned by the Airstory API. Additional logging has been added in the 1.1.6 release, and I'm going to work with @stevendluke + team to ensure the HTML export from Airstory is valid HTML.
Airstory received a support request this week, where the author would publish a document to WordPress and end up with a new, empty post (I've verified that it was indeed a blank post, and not Airstory erroring and showing a blank page).
The user was logged into WordPress (as evidenced by the fact that a post — empty or otherwise — was created. She tried it again the day following my email, and was unable to reproduce the issue (but had experienced it multiple times ahead of contacting support).
[Redacted] site report: