Main RSS Feeds for Send2Press Newswire:

Main feed (with inline images/media):
https://www.send2press.com/wire/feed/

“Clean” feed (without inline images/media; single image as enclosure):
https://www.send2press.com/wire/xmlclean/

“Clean” feed with Image (with single inline image, top of story; single image as enclosure):
https://www.send2press.com/wire/xmlcleanpic/

News by Industry:

Business News (all):
https://www.send2press.com/wire/business-news/feed/

Finance News (all):
https://www.send2press.com/wire/finance-news/feed/

Entertainment News (all):
https://www.send2press.com/wire/entertainment-news/feed/

Health and Medical News (all):
https://www.send2press.com/wire/health-medical-news/feed/

Charity/Non-Profit News (all):
https://www.send2press.com/wire/non-profit-news/feed/

Technology News (all):
https://www.send2press.com/wire/technology-news/feed/

News by Locale:

California News (all):
https://www.send2press.com/wire/us-news/california-news/feed/

Florida News (all):
https://www.send2press.com/wire/us-news/florida-news/feed/

New York News (all):
https://www.send2press.com/wire/us-news/new-york-news/feed/

Texas News (all):
https://www.send2press.com/wire/us-news/texas-news/feed/

The following WordPress plugins are recommended, based on our own experience. You may choose to use a different method.

FeedWordPress — this versatile plugin allows you to import RSS feeds from Send2Press into your news portal, and choose how to post, set author(s), and fully automate live posts.
» https://wordpress.org/plugins/feedwordpress/
Auto Post Thumbnail PRO — this modestly priced plugin ($14) is a proven solution for capturing the first image in our feed to add to your media database and assign as the “featured” image for the posts built with FeedWordPress. Seriously, we’ve tried other stuff and this one simply works. With most WP themes, your category and index module thumbnails are made from a featured image, so without that you’d have either empty boxes, or a fallback image which isn’t very attractive.
» https://codecanyon.net/item/auto-post-thumbnail-pro/4322624?ref=neotrope
Original Source Link:
If you wish to include the original source meta tag in your HTML header, you can add the following code to your WP theme (usually in header.php before the closing head tag). This basically pulls the source permalink custom field created by FeedWordPress so you can print in your meta data.
<?php if (is_single()) {$syndication = get_post_meta($post->ID, ‘syndication_permalink’, true);if (!empty($syndication)) { ?><meta name="original-source" content="<?php echo $syndication; ?>“/><?php }} ?>

This happens when you update theme or main WordPress …

nothing to fix; normally you will have one of these, unless hacker slamming that directory. So, with one you just mark as ‘fixed’ and move on.

That should so be in the WP documentation — which they are finally going to redo (won’t be called ‘codex’ any more for 2018!). 🙂

Basically turn stuff off unless absolutely necessary.

If you have 10 modules on your home page, use 6.

Turn off related posts, turn off trending ticker, turn off ‘more to read’, turn off ‘most popular 7 days’ option.

You might try that — and this might help in the process
https://wordpress.org/plugins/query-monitor/

learning curve involved in anything, so you’ll have to play with this.

I don’t work here, so can’t give you a step 1,2,3 as every site is different.

REMINDER – if you’re running one of the vulnerable version of WordPress, or vulnerable versions of Newspaper theme — you *will* get hacked.

PLEASE
a) check your theme version
b) if running vulnerable versions, or old WordPress:
— immediately run scanning software, to check for infection
c) make sure you have proper backups, even if infected
d) clean your website.
e) once fixed – make secure backups
f) then make a plan to regularly check versions and make proper secure backups

ONLY YOU CAN KEEP YOUR SITE(S) SAFE!

Usually you would need a plugin that does something like make an animated GIF from field frames from the video. Some websites test this — car websites for example — but they eventually abandon that as impractical and slow on mobile.

Probably need to write a function that appends the video into footer section of the AMP template being used. Likely ask the plugin author how to pull a custom field to print as part of the footer. Then try that with a function hook.

Best bet is to limit number of queries …
every module that has to go look up posts is a set of queries, mega menu with posts, news ticker, popular 7 days posts, fly out read next, related posts, more by author, etc. — all are queries. Try cutting back.

Whatsapp links only work on mobile and *if* you have the whatsapp ‘app’ actually installed — that’s how it works; clicking link without having Whatsapp ‘running’ will give broken link error.

Using any link-follower trying to follow that link basically means the link checker is too stupid to recognize whatsapp (kind of like W3C RSS checker that doesn’t understand srcset tags, or https enclosure images).

Presumably one *should* have rel=nofollow tags on those links, and didn’t look to see if they are there or not.

If you’re using the TD WPion/IonMag theme (also by TagDiv) – this isn’t correct forum for that.

• This reply was modified 8 years by simchris.

@betawin

did you try some of my suggestions?

several things you can do – limit number of queries, don’t use the mega menu with posts, limit number of module types in use; also dumb as it sounds adding the explicit URLs in your wp-config.php file helps too (see the wordpress codex docs on how to do that).

There was a bug in couple versions of theme, hence why always good to check the changelog for new versions, as I noted, for security flaws. Much the same with WordPress … huge number of people got hacked for WP 4.6 by not upgrading to version of 4.7 with all the patches.

So, one flaw allowed injection into the ad panel, solved by simply deleting the ad element; higher level had injection into all the pages via the dbase. So, both things needed to be checked per the links provided.

In any case, glad you got it sorted. 🙂

Just be sure to follow the links in the tutorial post I provided to ‘harden’ your site, as per the codex docs, etc. and you should be good.

Just *always* check changelog for any new updates to themes, plugins, WordPress, and DELETE all old unused themes, plugins — and properly update all things the right way (delete old versions, upload new versions, don’t merge by over-writing). Etc.

Well, did you *do* the items in my post, like search/replace in your dbase?

Did you properly update theme by deleting old folder, same with plugins and WP install?

Unless you scrub the infection from your dbase, it will be there forever.

Cheers.

Add your custom css to end of style.css then do this each time you update theme. Best way.

General rule is to use single quotes in headlines for publishing, and normal practice is for high-ascii chracters to be converted to HTML entities to not be broken greek letters. On our site, in English, when we share to FB, the titles come through fine with HTML encoding.

Depending on how you’re generating the OG tags for FB, there may be issue with the plugin or how you’re doing that.

Check your OG tags in the actual affected post to see what is actually there. FB can read HTML entities properly.

Did you test your pages with F12 to see if errors?

Google did start some big changes in August, moving stuff around, converting a lot of properties to mobile first (e.g., Google news undergoing transition to mobile first view even on desktop).

There was also update to the Automattic AMP plugin last month if using that, so change might have impacted something.

Also, as I understand it, not all pages get served as AMP versions by default since technically I think there is some usability threshold for it to get cached fully on Google’s edge CDN — but things change so much over there, hard to say.

Well, we aren’t using that for normal stuff.

It’s the way http/2 works on Plesk/Onyx — so, that is the minor hiccup we’re still sorting out. I think it has to do with the way that NGINX can run the code faster without the Apache layer, and yet grabs and compresses the code running on Apache to serve the cached copy in compressed format.

What’s funny is that I bugged Plesk/ONYX about adding some kind of security setup panel to navigate the complexity, and they added a ‘security advisor’ plugin/extension to do a one click setup. Nice. Have not yet tried it, though.

It may be with new version we don’t have to deal with the NGINX stuff anymore, but that was how it was done initially. I’ve been kinda waiting for improvements on that, with intention of making it the baseline for January 1, 2018. December will be the test month. Right now, it’s house cleaning for php 7 as we have a lot of old creaky shtml stuff to retire!

heh… yeah… we have CentOS on dedicated server also, and the funky thing is we run Apache, and http/2 under Plesk/Onyx has to run as part of NGINX … which sits in “front” of Apache … which is bizarre.

We’re still playing with this, since we are doing house cleaning to move fully from PHP 5.6 to 7.1x.

Too much fun! 😉

(( tested a page this morning normal page with photo + video, site branding graphics = 1.6 sec; AMP version of page, no video, no branding graphics 1.5 sec )) ….

SEE:
https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/

Wellll…. all our news is in Google News, and has been since 2005, without AMP 😉

And luckily AMP doesn’t create duplicate content issues, since the canonical link is designed just for that purpose and the AMP version links back to the real version to solve that (same way a print template does). With our old CMS on our big site, not using WP, and generating static shtml pages), we has static print and AMP pages, and both had canonical links, and the AMP template was built off the print template since there were not AMP plugins when we got started on that (and the main site didn’t use WP at that time, but now does).

For our news pages now (not using TD theme, but custom thing), we can load up the full news story with 2 images, logos, content, queries for related stories, etc., in 1.3 sec fully loaded. AMP version is quicker. But a scaled back print version would be just as quick.

All about the payload.

And with move to PHP7 + http/2 the speed will be even faster.

I guess we’re thinking over here that http/2 with a lean template would be better than AMP for user speed on mobile in the coming year. We’re playing with this anyway.

Doesn’t solve the page count issue — but of course Google wants you to run GA on AMP, and so that might even be the only truly workable solution for metrics on AMP pages.

Anyway — back to work before Labor Day holiday here …. cheers 🙂

titles on indexes, home page, sidebars are normally h3; sub heads on posts are normally h2 for primary, h3 for supplemental; titles on posts/pages themselves are h1 in the article section, not h3.

This is correct for SEO of news portals. A headline for linked news item on an index is h3 as it’s not the title of the index page, nor is it a supplemental headline for that page (such as a description for the category index).

Since amp ‘forbids’ client side scripting, it may be they are blocking anything being ‘run’ — or it may be that it runs first time, but then when cached on Google’s CDN for edge loading, the element script can’t run, as it’s not actually on the CDN.

There are folks doing stuff with Ajax with AMP for refreshing origin content; which is a bit like expiring the bucket on a CDN to refresh the local copy of content.

Personally, I’m of a mind, that AMP is an interim solution while wifi speed and phones play catchup. For instance, a new iPad PRO is more powerful than a 10 year old PC that HTML5 was built for.

In theory, one could argue that simply building your own print template with lean code, your desired custom elements like forms, or related post, or video, or whatever, could be ‘dressed down’ to lowest form like a print template, serve that for mobile and not even use AMP. Speed would be the same, especially if you’re already using CDN — and having a lightning bolt in SERPS doesn’t mean your page is better than everybody else’s page, just that it’s compatible, and might not even show up in SERPS, with all other things being equal with relevance, site age, content, etc.

Does the user experience suffer with AMP? Then why use it?

Questions for another time and place probably, but after nearly 2 years since the BETA, we’re kind of re-evaluating this for 2018, frankly.

Just more ramblings … 🙂

I never remember where that is either ?

Check system status first.

Yes, well — theme doesn’t manage your open graph settings, image compression level, server speed, IP blocking, Facebook API, etc.

All you can do on theme and plugin side is add the tags, check that FB can access them, adjust anything breaking the tags, or blocking loading of images, etc., and then it’s up to FB to capture the content.

You cannot pay them or force them or berate them — they don’t care; you’re not paying them to grab your posts.

I’ve been in the beta FB stuff since FB first launched, and this is a recurring issue. But there you are.

Setup your FB developer account, check your posts, code, etc., learn to clear FB cache of your post if it’s hiccup-ing, check your page speed carefully, caching, image speed, etc. — all that stuff impacts FB being able to get stuff “quick.” A 600×450 image that is 35kb will be more likely to get captured properly than a 350kb image the same size, for example.

Anyway, good luck.