eric2236

Hello @webcraftic. Can you help me please?

Yes it is. Is there anyway to continue with my current snippet so I don’t need to edit thousands of pages? What does no longer support mean? Will my ancestry charts no longer appear on my pages?

Just tried to publish a snippet and got this error message.

Don’t Panic
The code snippet you are trying to save produced a fatal error on line 3:

require(): Failed opening required ‘Ancestry.php’ (include_path=’.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php’)
The previous version of the snippet is unchanged, and the rest of this site should be functioning normally as before.

Please use the back button in your browser to return to the previous page and try to fix the code error. If you prefer, you can close this page and discard the changes you just made. No changes will be made to this site.

Are you talking about my access token? What is a key? How do I make a new key?
I think I would be getting the “rate limit reached” alert if i was getting too many hits. This error is specific to GET photo-id reaction.

You might need to upgrade the feed them social API to the new version

Your App, FTS Feed, is currently accessing Graph API v2.3 which will reach the end of its 2-year lifetime on 10 July, 2017. We estimate 27 endpoints that FTS Feed calls will be impacted by this change and may stop working after the automatic upgrade push. To ensure a smooth transition, please migrate all calls to Graph API v2.4 or higher. Use the API Upgrade Tool to understand exactly how this change will impact your app.

Note: If you do not see any impacted calls in the API Upgrade Tool, your app/code may not be affected by this upgrade.

That’s not the issue Damon. Got the email again from facebook.

Your app is receiving errors from GET {photo-id}/reactions

In the last three hours 100% of the calls to the method GET {photo-id}/reactions resulted in errors.

Error Code

12

Error Description

Unavailable in this version

Error Count

2253

This may be result of a recent change you made to FTS Feed, or a failure to comply with a recent breaking change.

For more information about error codes and recovery tactics, please visit our documentation.

If the error rate has not been resolved after 3 days, we’ll send you another alert.

You can view this and other Developer Notifications related to your app, in the App Dashboard.

Hi Damon,

I use many different shortcodes for hundreds of feeds. The main format I use is.

[fts_facebook id=XXXXXXXXXX posts_displayed=page_only type=page]

I’m not sure where the problem is occurring because I use this plugin on dozens of blogs. How do i narrow it down?

### Begin System Info ###

SITE_URL:
Feed Them Social Version: 2.1.8

— WordPress Configuration:

WordPress Version: 4.7.5
Multisite: No
Permalink Structure: /%postname%/
Active Theme: Limuso 1.1.2
PHP Memory Limit: 512M
WP_DEBUG: Disabled

— Webserver Configuration:

PHP Version: 5.6.30
Web Server Info: LiteSpeed

— PHP Configuration:

Safe Mode: No
Upload Max Size: 250M
Post Max Size: 250M
Upload Max Filesize: 250M
Time Limit: 30
Max Input Vars: 1000
Allow URL File Open: On (0)
Display Erros: N/A

— PHP Extensions:

FSOCKOPEN: Your server supports fsockopen.
cURL: Your server supports cURL.

— Active Plugins:

Adminer: 1.4.5
Akismet: 3.2
API KEY for Google Maps: 1.1.0
Custom Content Type Manager : Advanced Custom Post Types: 0.9.8.9
Disable Feeds: 1.4.4
Disqus Comment System: 2.86
EWWW Image Optimizer: 3.1.3
Fast Secure Contact Form: 4.0.50
Feed Them Social (Facebook, Instagram, Twitter, etc): 2.1.8
Feedzy RSS Feeds Lite: 3.0.5
Google Places Reviews Pro: 1.5.3
Insert HTML Snippet: 1.2.2
Leverage Browser Caching Ninja: 2.1
Mail Subscribe List: 2.1.3
PHP Code Widget: 2.3
Process Site Map: 0.3
RSS Just Better: 1.4
Simple Cache: 1.6.2
Simple Google Maps Short Code: 1.3
Simple Taxonomy: 3.5
Simple Wp Sitemap: 1.1.7
Special Recent Posts FREE Edition: 2.0.4
Sucuri Security – Auditing, Malware Scanner and Hardening: 1.8.3
UpdraftPlus – Backup/Restore: 1.12.37
WP-FileManager: 1.4.0
WP-Nicescroll: 2.0.0
WP Htaccess Editor: 1.3.0
WP Simple Rss Feed Reader: 0.8.1

— Custom Token or Keys added to Options Pages
— You must have a custom token to use the feeds

Facebook App Token: Yes
FB App ID for Like Button: No
Twitter Consumer Key: Yes
Twitter Secret: Yes
Twitter Token: Yes
Twitter Token Secret: Yes
Pinterest Token: No
Instagram: No
YouTube: No

— Offset Post Limit:

Offset Facebook Post Limit: None
Hide Notice on Front End: Yes

— FaceBook & Twitter Date Format and Timezone

Date Format: No
Timezone: No

— Fix Twitter Time:

Fix: No

— Disable Magnific CSS:

Fix: No

— Fix Internal Server Error:

### End System Info ###

here is some of the code i could find related to sharethis.

<?php if( is_single() ): ?>
<script>var switchTo5x=true;</script>
<script src=”https://w.sharethis.com/button/buttons.js”></script&gt;
<script>stLight.options({publisher: “ur-6568e777-919c-a5dd-ac31-98a6fa2e6b2d”}); </script>
<?php endif; ?>
<?php do_action(‘wp_seo’); ?>

You may not call it malicious code but I do. ShareThis wouldn’t have bought the google analytics plugin from the original private creator if you didn’t have a motive. That motive was to use the current users to provide you with data on their blog visitors and enhance your business. It’s the simplest plugin and you could have built it yourself and put it in the plugin directory within a couple days. Instead you created an update that changed the original creators plugin to install scripts into the header of everyone’s blog.

The plugin and all it’s data are long gone from my blog. If I remember correctly one was ps.eyeota.net. Don’t play dumb. I’ve had this same problem with your sharethis button injecting scripts into my header file too. There were 3 scripts that I did not authorize which this plugin in question added to my code.

• This reply was modified 8 years, 2 months ago by eric2236.

The whole line in validator reads “The implied layout ‘CONTAINER’ is not supported by tag ‘amp-font’
AMP_LAYOUT_PROBLEM

In addition. I have received this message in search console.

Google systems have detected that some of your AMP pages do not meet our guidelines and will therefore not show in Google Search AMP-related features. The following report provides examples of pages with errors:

Issue: invalid structure data element.

It’s just a standard blog post page.

Thanks for your note. My sidebars have more than just ads. They have rss feed content, recent posts, archive posts, menus. etc. How do I get amp supremacy to display my sidebar content in the amp compatible pages? Thank you.

Tell me more about the custom taxonomy. Do I need to be a theme developer to set this up and edit the code? Or can it be manged with a plugin?

thanks I will consider using tags.