Error : General Fatals: Sorry, We Couldn't Parse the Article

Viewing 15 replies - 16 through 30 (of 32 total)

  • I got a reply from FB saying they had fixed the issue but it doesn’t look like it. We’ve been super busy this week on some other stuff, but we’ll probably switch to a different plugin to see what we can do.

    We’re seeing no way to tell the plugin what NOT to send, and it’s attempting to send Pages, Posts, and pretty much anything at will is not really a workable solution either, since we don’t want to publish every last thing we create or update. Weird.

    Hi,

    exact same problem here ??

    Hello everyone. Thanks for all the collaboration and patience on this thread!

    The general assessment reached by many is correct in that the error is shown for articles submitted/edited while the review process has been initiated.

    An important observation to note is that the error doesn’t necessarily mean that there are problems with the markup within your article. It should definitely be communicated better so we appreciate the feedback.

    mdiakiv
    bobderrico
    kimstuart
    Rizal
    kristajune
    singletrackmark
    lecs81
    Namli
    n3rdabl3
    nealffischer
    circlecast
    Recyclart

    … and everyone who has experienced this error message: could you please report if the error is shown again once you are no longer under the review process?

    @kimstuart, your request to be able to control articles which are not sent to Facebook has been logged as a feature request on GitHub: https://github.com/Automattic/facebook-instant-articles-wp/issues/186

    @n3rdabl3, I’m curious to know if you are still observing “blank” content in some articles since there have been other reports of this behaviour which I suspect is not related to the issue in this thread.

    @nealffischer, thanks and we appreciate your patience. Are you still under review?

    Hey @paulo, That’s right, for a few days we were observing blank content other than the title and the main image, however things have since corrected themselves and content is once again showing.

    We’re now just waiting the 3/5 working days for them to hopefully approve our content!

    I think you’re right, the approval process seems to put a hold on the Instant Articles plugin. I’ll keep you posted if we’re eventually approved (this time there should be no problems… hopefully.

    @paulo – was just approved last night. Still trying to learn all the ins and outs. Some of my articles are still getting the parsing failures some aren’t All of them were at one point so that’s progress. I got approved on the second attempt. One thing I have noticed. Facebook doesn’t like not having the 

    <!doctype html>
<html lang="en" prefix="op: https://media.facebook.com/op#">

    at the top. For some reason I have had to go back and manually add that at the top of each article.

    Glad to hear you guys are on track to being approved.

    @nealffischer, I think your comment regarding the <html> tag deserves some looking into because it’d be better if you didn’t have to make unnecessary changes to all your articles. Could I ask you to open a separate issue for this?

    I got the fatal errors to start to go away.

    What I had to do what add

    <!doctype html>
<html lang="en" prefix="op: https://media.facebook.com/op#">

    Then, I went through and spread out the html tags. Easier to show rather than try to explain.

    <!doctype html>
<html lang="en" prefix="op: https://media.facebook.com/op#">
<head>
    <link rel="canonical" href="https://*.url/news/title/"/>
    <meta charset="utf-8"/>
    <meta property="op:generator" content="facebook-instant-articles-sdk-php"/>
    <meta property="op:generator:version" content="1.0.6"/>
    <meta property="op:generator:transformer" content="facebook-instant-articles-sdk-php"/>
    <meta property="op:generator:transformer:version" content="1.0.6"/>
    <meta property="op:markup_version" content="v1.0"/>
    <meta property="fb:article_style" content="default"/>
  </head>
  <body>
    <article>
      <header>
        <figure>
          <img src="https://*.com/images/*.jpg"/>
        </figure>
        <h1>ELCA introduces initiative to address voting rights</h1>
        <time class="op-published" datetime="2016-04-12T23:13:05-04:00">April 12th, 11:13pm</time>
        <time class="op-modified" datetime="2016-04-20T14:02:09-04:00">April 20th, 2:02pm</time>
         <address>
              <a href="https://*.url">*.url</a>
         </address>
      </header>
      <p><i><b>By Mr. So Andso</b></i></p>
      <p>text</p>
      <p>text</p>
      <p>text</p>
    </article>
  </body>
</html>

    Many times the plugin seems to minify the html and scrunch it together. Those almost always throw the fatals error.

    Hello,

    any solution here?

    I have the same issue.

    WordPress 4.5.1
    PHP 5.6.12
    Plugin 2.10

    Any help?

    Thanks
    Sebastian

    Sambuno

    (@goldmaverick)

    I have the same issue.
    I’m running the most wp 4.5 and the recently released version of the plugin.

    General Fatals: Sorry, We Couldn’t Parse the Article: Don’t worry, we are looking into this! Please try again shortly.

    same issue any help here?????

    Sambuno

    (@goldmaverick)

    @paulo mentioned we should wait untill we are out of review. So I’ll see if that clears it

    Indeed, the common issue in this thread occurs for articles submitted/edited while the review process has been initiated. There are already other issues reported for improving the messaging to communicate this detail better so I’ll mark this thread as “resolved”.

Viewing 15 replies - 16 through 30 (of 32 total)
  • The topic ‘Error : General Fatals: Sorry, We Couldn't Parse the Article’ is closed to new replies.