Thomas Townsend

This issue was NOT resolved with 4.0.8 it’s still broken

Update: The issue is your 4.0.1 conflicts with
https://www.ads-software.com/plugins/simple-share-buttons-adder/

If I deactivate that plugin Chatbot works.

Please coordinate with simple share plugin dev to fix your chatbot.

Yes -AMAZONPOLLY-ONLYAUDIO-START- Follow the link and you can see its getting picked up on the widget

I had this set to content limit to show the first 150 characters of the post but it’s showing the -AMAZONPOLLY-ONLYAUDIO-START- that is supposed to not show? For now, I have set it to only display the Title. Appears your plugin is in conflict with Genesis Theme
“Featured Post Widget”

• This reply was modified 6 years, 9 months ago by Thomas Townsend.

Divi theme was updated on 5/20 to 3.3.1

I am not a Divi guy and I did test after the update and all seemed to work ok until we UG to 2.8.5 – can I delete current and go back? where can I obtain 2.8.4 version to test,

Still having an issue prior to the 7.3.10 update the shortcode I used on specific job pages was working correctly and the css I used for spacing was spot on. now it’s a hot mess. Would appreciate if you could review this

This is an example custom post where the alignment is now whacked.
https://www.strategicrecruitmentsolutions.com/jobs/techie-paralegal-2/

Not sure what the developer did with version 5.0.3 but it’s still not resolved the issues previously reported. It’s still incompatible with WP 4.9.4 – still broken.

False Flag. When I deactivated the plugin earlier to test another issue on clients site. When I reactivated the plugin it appears to have lost the credentials and I had to reconfigure again.

On a similar note: When you enter the Admin screen for the first time, both fields appear to have been auto-populated with my WP Admin Login creds. I know to delete this and add the ones for AWS but someone else may be confused by this.

Suggest you add placeholder text in the next version until the correct creds are added and saved.

This is really an AWESOME job the WPEngine/Amazon team did on this plugin.

• This reply was modified 7 years, 1 month ago by Thomas Townsend.
• This reply was modified 7 years, 1 month ago by Thomas Townsend.

If you’re getting that error you may have missed a Step:

amazon-polly-wordpress-plugin

6. On the second step of the wizard provide the name for your policy: PollyForWordPressPolicy and create it.
7. The next step will be to create an IAM User. To do this, on the left menu choose ‘Users’ label. There click on ‘Add User’ button.
8. Provide a name for your user, for example, “WordPress” and select “Programmatic access” option. Go to the step number 2.
9. On the “Permission” step, choose ‘Attach existing policies directly’ option, and then on the list provide the name of the policy which we have created in step 6 (PollyForWordPressPolicy).
10. On the “Review” step click on “Create User” button.
11. On step, you will see information that the user was created. You need to note “Access key ID” and “Secret access Key” – you will need to provide them on the plugin configuration page.

It doesn’t matter what you name your User (this is a Managed Policy User) I named mine after the client’s Blog. You DO NOT Use your Admin or any other human user for this.

Once you have created that User you attach the PollyForWordPress Policy and use the credentials you created for that User.

As an addition to my post above. This is clarification for the Developer.

The site in question I have corrected by reverting back to the previous version 5.0.1
I have a copy of the site on a staging server that is publicly accessible installed with current version 5.0.2 and can make both of those URL’s (links to the websites) Staging and Live available to you should you like to View the sites to ascertain whats happening.

If you’re interested contact me on the WP Slack Forum and I will provide the links.

NOTE:For those that may misread my intentions. This is NOT an offer to provide you login creds. Just view the site via a publicly available link. I am not sharing those links in this post as I don’t want to drive artificial traffic to a clients site that is running GA Campaigns.

5.2 was working fine with WP 4.9.2 and is broken with 4.9.4

I did the needful and deactivated all plugins to test for conflict and have no conflict with any other plugins or theme. When I revert back to plugin version 5.1 the issue is resolved. So something in the update to 5.2 does not work well with the current version of WP (4.9.4)

[redacted]

• This reply was modified 7 years, 1 month ago by Steven Stern (sterndata).

The site has NOT been hacked rather one of my associates was testing a plugin that had been hacked and that’s where the ad came from. Very much appreciate you bringing this to my attention. Said associate is now banned from Live site updates and should have known to test on staging. The offending plugin was removed and we did a full scan of the site and it has come up clean.

Suggest you clear your browser cache and you should now be able to access the documentation area.

Ouch that iFrame looks really bad – can’t help with a non WP frames page

Wrong Plugin – can’t help you there

• This reply was modified 7 years, 5 months ago by Thomas Townsend.

Wrong plugin.

Allowing or Not allowing comments is a function of your General Setting and how you have the default page layout set-up on your site and NOT Job Manager.