kimstuart

Hugh? Any ideas on the problem here?

Excellent, thanks so much!

Thanks for clarifying, but we still don’t have any of that in the posts. We keep them super basic so the feed works for FBIA and Apple News.

Not sure what this new error is or where it comes from.

“Sometimes I’ve seen it from a stupid malformed Google as or YT video!”

malformed Google? What is that?

We don’t have any youtube or other videos on the pages, nothing has changed on them since they didn’t have issues a week or two ago.

Is the user that accesses the podcast from iTunes (for instance) actually doing an onClick action that is a download? I’m a little confused as to exactly what happens with someone from iTunes accesses the mp3 file compared to what happens when someone is on the site and clicks “Open audio player in new window” for example.

Bueller? Anyone? ??

Super, thanks much, I’ll be on the lookout for the plugin update and expect it to clear up.

Otherwise, fantastic plugin, beats the daylights out of the FBIA one that’s from the big names.

Weird, I just got an email from G about some posts that haven’t been touched in more than a month –
The attribute ‘lgtitle’ may not appear in tag ‘a’.”

FIGURED THIS OUT… if you use any kind of relative links in the URL structure – /content/article without the full domain, this is what comes back.

I’ve got a new error now – and I’m clueless as to how it’s happening. I thought it was perhaps because the slug was long, but I’ve edited the slug and it’s still showing this issue.

The server responded with the following messages:

URL is Incomplete: The URL used for this media element is missing information. We have automatically filled in information for you. Please check that the URL is now correct and complete.

Same here. It’s a it confusing. Otherwise fantastic plugin!

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.

I’m not going to change my review or my opinion, this is a terrible plugin.

Yes, that fixed it, thanks ??

We have same on some posts.

We have this problem as well. It appears to be fine when the initial submit is done but then later the content says it’s empty or it can’t parse.

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

Obviously there’s no way to link to anything that shows the problem, but I have screenshots I can put up if you need them.