mda1125

Turned on Debug and installed the Plug-In
Clicked Activate

Fatal error: Uncaught Error: Class ‘SimpleXMLElement’ not found in /var/www/html/wp-content/plugins/amazon-polly/vendor/aws/aws-sdk-php/src/Api/Parser/PayloadParserTrait.php:39 Stack trace: #0 /var/www/html/wp-content/plugins/amazon-polly/vendor/aws/aws-sdk-php/src/Api/ErrorParser/XmlErrorParser.php(28): Aws\Api\ErrorParser\XmlErrorParser->parseXml(Object(GuzzleHttp\Psr7\Stream)) #1 [internal function]: Aws\Api\ErrorParser\XmlErrorParser->__invoke(Object(GuzzleHttp\Psr7\Response)) #2 /var/www/html/wp-content/plugins/amazon-polly/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php(174): call_user_func(Object(Aws\Api\ErrorParser\XmlErrorParser), Object(GuzzleHttp\Psr7\Response)) #3 /var/www/html/wp-content/plugins/amazon-polly/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php(100): Aws\WrappedHttpHandler->parseError(Array, Object(GuzzleHttp\Psr7\Request), Object(Aws\Command), Array) #4 /var/www/html/wp-content/plugins/amazon-polly/vendor/guzzlehttp/promises/src/Promise.php(203): Aws\WrappedHttpHandler->Aws\{closure}(Array) #5 in /var/www/html/wp-content/plugins/amazon-polly/vendor/aws/aws-sdk-php/src/Api/Parser/PayloadParserTrait.php on line 39

I can get the logs (if you can provide me the best location and logs to provide)

I installed WordPress myself using this tutorial. It was not baked into the AMI.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hosting-wordpress.html

Unchecked the Media option
Created a test post
Deleted the test post
Rechecked the exclude media option

Now all 3 sitemaps show (post, page, category).

Maybe just the re-selection of options regenerated the sitemap.

I see this in FB for every post:

Content Type reported: text/html; charset=UTF-8
Media enclosure not created because: The content type returned from your host server was a text type, not a binary media type. Podcast content should always return a binary media type, such as audio/mpeg for audio, or video/mpeg for video.

I’ve checked my host and indeed there is a proper content type setup. I’ve also checked Amazon S3 and again, it’s setup.

Well said.

I used Contest Domination for a while. But it broke with WP 3.8. Maybe even before that but I really noticed it when I upgraded.

There’s no support for it. They want you to go to the cloud based $99 contest subscription.

Heck no. Plug-in was good while it lasted but they migrated to some high priced model.

I’d be interested myself in another viable one.

I sent a bug report to Cloudflare.

Rocketship (Rocketloader) greatly improves the speed at which scripts load. It’s not impossible it’s causing some type of issue with this script.

Rocketscript comes from Cloudflare. It’s an optional feature that speeds up the site but you are correct, it is enabled and could be messing up the player.

I’ll contact Cloudflare and see if they can assist.

Thank you. This fixed my issue as well.

Resolved:

Opened a ticket with my host. They were denying Feedburner for whatever reason. Once they unblocked it, I did Resync and received a successful confirmation.

Issue was… host was blocking Feedburner.

Wondering if I need to open a ticket with my webhost? Maybe they blocked Feedburner for some reason?

This original feed works in my browser so I don’t think it’s a universal 403 error.

The original WP feed shows the most updated information.

It’s just Feedburner having a problem and the support for that product is gone.

Solved:

I still am not certain why but I once again cleared the browser cache on IE and Chrome and it is now working! Maybe it was the updated files and I did not clear my cache?

In any case, case closed.

Genius..

Had the issue tonight. 1st search term on Google and I found this.

All I did was edit my wp-config.php file by pasting that line of code. Saved the post and Podpress is back up and running.

Thank you very much.

I tried using version 1.0 of Twitter Tools. That didn’t seem to make a difference.

You’d think even with the time difference, it would eventually be posted as a daily digest. But in fact nothing happens.

The sidebar works fine. Twitter is working fine. Just no daily digests after the Twitter API issue.

It started working after that, then a few days later quit and that’s it.

Glad it’s not just me.

Same for me.

Yesterday it was working fine. Today, no Tweets?

Checked the Twitter Options and it keeps saying wrong username/password.

I go to Twitter, use the same username and password and it’s fine.

Sadly I cannot offer any assistance but I am glad to see I’m not alone.