For trackable stats you likely need to be using an advertising management platform.

Did you test your AMP pages work; and also test them with the AMP tools online for compliance?

AMP won’t support certain sites due to various failures or guidelines/requirements outlined on the AMP support site.

Tested on: May 14, 2019 at 3:13 PM
Page cannot be reached
This could be because the page is unavailable or blocked by robots.txt

https://search.google.com/test/amp

https://support.google.com/webmasters/answer/6340290

The default official AMP plugin from Automattic works great with the theme and has since day one; so that is obviously a good fallback for mission critical sites to work with AMP.

Of course no AMP plugin will fix issues within content that are pre-existing and not AMP-compatible (like inline HTML in some cases, inject javascript or other code where not supposed to be; rogue plugins, et al.).

Some sites moving away from AMP, as Google now trying to make it a “publishing platform” to monetize for showing content as an application, vs traditional web formats. For many folks, simply having mobile friendly optimized responsive site may be better choice unless very high traffic with ads non-blocked via AMP when cached on Google cloud.

For “most” bogs, AMP has no benefit for the user or site owner.

My two cents anyway; having been using it since it was in BETA and following Google’s latest zig zags with trying to get people to adopt this format for their entire sites, which is impractical and perhaps stupid to buy into a Google concept that might be abandoned at some point while traditional responsive pages will work forever.

WP includes basic built-in music player; so might try that first?
See the WP ‘codex’ (docs) for using multimedia.

you might also find this article (not mine); helpful if new to WP:
https://www.hostinger.com/tutorials/wordpress-audio-players/
https://themeisle.com/blog/create-wordpress-audio-playlist/
https://www.wpbeginner.com/plugins/9-best-audio-player-plugins-for-wordpress/

• This reply was modified 7 years by simchris.

We found a pretty good one for Twitter, but nothing usable for FB.

https://wordpress.org/plugins/twitter-auto-publish/

Been using this for couple of months now on several sites, and have had no issues; only minor quibble was not getting straight answer from author on whether or not using the built-in WP shortcode (story ID) in the published tweet would work — and, it does. (author was like “why would you want to do that” or “twitter will change to shortcode” — which were both incorrect answers to my post in the support forum for the plugin…).

Of course if you don’t understand how to setup/connect an API from your site to twitter, you won’t be able to use it; but we have it working on couple of sites when finally giving up on Feedburner (stop laughing…) 😉

For all amp plugins you need to resave permalinks to create the /amp endpoint redirect.

For all AMP plugins you need to re-save your permalinks to create the /amp endpoint redirect.

FYI:
There is actually a problem with *all* Facebook embeds which started this past week, as we have a report dashboard for clients where we paste in the URL for FB posts to show them how we share their content; those also stopped working, and it’s not theme related in any way. Twitter embeds work.

It’s almost like FB ‘broke’ all their embeds for simply pasting a link to something into a WP WYSIWYG box in WP post editor and/or a custom field, like with ACS PRO.

So — it’s NOT theme related; we’re seeing broken FB elements “everywhere” this week.

There is actually a problem with *all* Facebook embeds which started this past week, as we have a report dashboard for clients where we paste in the URL for FB posts to show them how we share their content; those also stopped working, and it’s not theme related in any way. Twitter embeds work.

It’s almost like FB ‘broke’ all their embeds for simply pasting a link to something into a WP WYSIWYG box in WP post editor and/or a custom field, like with ACS PRO.

So — it’s NOT theme related; we’re seeing broken FB elements “everywhere” this week.

Some background from the various blog posts on this topc —
upshot, you need to research whether it applies to you, or not, or just good idea for 2020.
——– excerpts from various blog posts:

ADA is short for the Americans with Disabilities Act, which became law in 1990. It prohibits discrimination against individuals with disabilities in all areas of public life. The ADA, at least for Title III (private sector businesses), only applies to companies that employ 15 or more persons.
https://hackernoon.com/ada-compliance-lawsuits-and-your-web-presence-797ef03cdef2
————————–

5 Reasons Your Website Should Be ADA Compliant. The Americans with Disabilities Act (ADA) was developed in 1990 and is meant to ensure that people with disabilities have the same opportunities as anyone else. … Recently, a ruling has been passed declaring the official standard of website accessibility for businesses.
https://blog.cws.net/5-reasons-your-website-should-be-ada-compliant

Who Needs To Be Compliant?
The general consensus right now is that any business considered a “public accommodation” should have an ADA compliant web presence.

“Public accommodation” could apply to most things depending on who is making the interpretation. Generally, however, this would refer to B2C, retail, or any business the general public should be able to use, understand and access easily.

The judgment against Winn-Dixie was determined after the courts felt that the website was too heavily integrated with the physical store presence. This could have been prompted by things like placing their weekly ad on the website.
———————————-

• This reply was modified 7 years by simchris.

There is an ADA compliance plugin for WordPress worth looking at.
However, some stuff might be considered questionable; for example for ADA Compliance, it’s likely bad form to continue using title tags for images in addition to alt tags, even though we’ve been doing that for SEO for years, and because some of us like the hover function for a label. However, this should not be abandoned as bad for ADA, and really useless for SEO (basically start using proper captions!).

Stuff like that. Some of the ADA compliance stuff is, ironically, already included in the ‘audit’ usability score stuff in Chrome/Lighthouse — this is where some of that tap target and stuff too tiny to read warnings come from.

So I’ve been telling folks
(1) run audit for ‘usability’ with Chrome (F12 – audit) and learn what the stuff means to get 100% ‘usability’ score
(2) run the ADA Compliance plugin for WordPress to at least start looking at options — https://wordpress.org/plugins/wp-ada-compliance-check-basic/

(I have no relationship to the TagDiv folks other than having been around here since they launched; and have no relationship to the plugin noted)

Did you resave your permalinks after enabling AMP ?

Also remember that you need to change the memory setting in
BOTH:
a) server settings, memory allocated to php
b) in your wp-config file, to expressly specify memory amount

The minimum size for an image for AMP support is 696 pixels for the old methodology; meaning any image placed into a post smaller than that, will not meet AMP requirements, but may still be used. They are moving to a larger size which I think is something like 1200pixels, but we’re still using 696 pixels for our images (or 700 pixels), without any trouble with AMP.

If you have legacy pages with images 500 pixels wide, or old old 400 pixels wide; those are not AMP compatible and will generate warnings.

Just some feedback as we went through this with our legacy pages from prior to 2016 going back to 2005 !

Also, checking error logs on server is helpful if things ‘suddenly’ crash without warning. Also check into security hardening your WP install to stop resource hogs from hack attempts.

Usually good to check the Yoast SEO support forum on WordPress.org for other reported problems that seem to happen right after a new major version of Yoast (e.g., v10 …) invariably a day or two later you will see a 10.01 then a 10.02 to fix the bugs from the fixes! Seriously.

Are you using the classic editor plugin included with WordPress 5 ?
If you have that set to on, then Gutenberg won’t load.

Akismet is super useful … we use it here.

Not theme error. This is an issue with how WordPress works when running an update, it may reveal the path to the theme as part of the redirect when the main WP content being updated — normally only way to avoid this is to use a “maintenance” plugin prior to doing WP core and plugin updates.

Simply mark fixed and move on. It’s not an actual error, and it “should” cause error, as nobody should actually try to visit/read that location on the web.

This really should be in the core WordPress documentation after 15 years (sigh).

In case anybody is worried, I just tested Newsmag 3.x with PHP 7.3.2, WordPress 5.1, http/2, and still works ! 🙂

Also note that 7.3 is optimum high performance ‘recommendation’ — it is *NOT* the minimum required.

WordPress 5.1 still works just fine on patch PHP 5.6 *PATCHED* version, but now deprecated and should move ahead asap, and works very well on PHP 7.2x. SO, if you’re running PHP 7.2x you are fine for those waiting on the next dot revision of 7.3x.

Are you on desktop or mobile? Whatsapp is a ‘mobile only’ platform.

Note the latest Yoast update 2/12/19 may fix the issue. Be sure to try that.

If style sheets ‘not loading’ — that is not a theme problem but system problem.

So, good to check F12 console view for errors, to ensure content actually loading.

Also try testing with GTmetrix.com — test as single post — and see if you have any issues with your setup.

Obviously if mobile styles are not loading, then desktop version would load for mobile as the responsive CSS needs to actually be there.

Common issues are mixed content – meaning some elements load via https, some set for http; or files not actually there.

a) update plugins at same time as theme; they do not update automatically
b) READ the changelog to see what changed prior to update — so, for example if it says ‘child theme changed’ — you may need to re-apply changes to child theme (why I don’t use them)
c) choose whether to update AFTER you look into what changed

ALWAYS MAKE DBASE BACKUP VIA HOSTING CONSOLE PRIOR TO ANY THEME UPDATE.
ALWAYS MAKE FTP BACKUP PRIOR TO ANY MAJOR THEME UPDATE.