AMP

Omschrijving

Deze plugin voegt ondersteuning toe voor het Accelerated Mobile Pages (AMP) project. AMP is een open source initiatief die als doel heeft geoptimaliseerde mobiele inhoud te leveren wat direct wordt geladen.

Wanneer deze plugin geactiveerd is hebben alle berichten op je site een dynamisch genereerde AMP versie, bereikbaar door het toevoegen van /amp/ aan het einde van je bericht URL. Bijvoorbeeld, als je bericht URL http://example.com/2016/01/01/amp-on/ is kan je de AMP versie benaderen via http://example.com/2016/01/01/amp-on/amp/. Als pretty permalinks niet actief zijn kan je hetzelfde bereiken door ?amp=1 toe te voegen zoals: http://example.com/2016/01/01/amp-on/?amp=1

Note #1: that Pages and archives are not currently supported. Pages support is being worked on.

Opmerking #2: Deze plugin maakt alleen AMP inhoud, maar toont deze niet automatisch aan de bezoekers als deze de site bezoeken via een mobiel apparaat. Dit wordt geregeld door AMP gebruikers zoals Google zoeken. Voor meer details, zie AMP Project FAQ.

Volg of help met de ontwikkeling van deze plugin op https://github.com/Automattic/amp-wp

Schermafdrukken

Installatie

  1. Upload de map naar de /wp-content/plugins/ map
  2. Activeer de plugin via het ‘Plugins’ menu in WordPress
  3. You may need to refresh your permalinks by going to Settings > Permalinks and tapping the Save button.

FAQ

Hoe kan ik de AMP uitvoer voor mijn site aanpassen?

You can tweak a few things like colours from the AMP Customizer. From the Dashboard, go to Appearance > AMP.

For deeper level customizations, please see the readme at https://github.com/Automattic/amp-wp/blob/master/readme.md

What about ads and shortcodes and such?

Check out https://github.com/Automattic/amp-wp/blob/master/readme.md#handling-media

What about analytics?

Many plugins are adding AMP support already. If you handling analytics yourself, please see https://github.com/Automattic/amp-wp/blob/master/readme.md#analytics

Google Webmaster Tools is reporting validation errors for my site. How do I fix them?

The best place to start is to open a new discussion in the support forum with details on what the specific validation error is.

Why aren’t Pages supported yet

A wise green Yoda once said, “Patience you must have, my young padawan.” We’re working on it 🙂

Beoordelingen

No support

Zu Beginn wars ein gutes Plugin. Und dann startete das Problem mit den Umleitungsfehlern. «To many redirections» und mein Blog konnte nicht mehr aufgerufen werden. Nach mehrmaligen Kontakt-Versuchen mit dem Support, der leider nicht geantwortet hat, musste ich das Plugin deaktivieren.

Lasst die Finger von diesem Plugin.

No Adsense Support & Adds WordPress link

Very dissapointing that Automatic appear not to be updating this plugin.

There is no adsense support so if you start using AMP you will need to edit the code yourself to reintroduce your Adsense code – very unsatisfactory.

Also, the plugin adds a link at the bottom of every page to wordpress.org – WHY?!

Come on Automatic get your act together

Broke my site, unfortunately

The plugin created a beautiful /amp version of all my blog posts, but unfortunately these pages did not trigger on mobile, and it slightly off-centered many elements site-wide, which can not be fixed.

It DID work just fine on another site I built which uses a different theme, so the theme might have something to do with it. Again, though it didn’t mess up the layout of this second site, it still does not trigger the amp versions of the pages (maybe this takes time?).

60% of my AMP posts have Critical issues

I use this plugin and Yoast’s Glue AMP Plugin. Automattic (this plugin creator) has been an amazing part of my web experience in the past.

3/22/07 update: Now just under 20% of my posts have critical issues. I think the fact that I added text (a phone number) in the Yoast glue plugin where the design header is may have caused the critical error issue.

Update after I initially post this: When I manual do the Google AMP test on a few randomly chosen on AMP URLS (for which Webmaster tools said they had errors just 1 hour ago), Google says each Valid AMP page.

Per Google Webmaster Tools yesterday, 60% of my AMP posts had critical issues. Prior to the update above, I expect this % to rise.

Each post has these 5 critical issues

Issue Severity Pages with issues
1 AMP markup missing or incorrect Critical
2 User-authored JavaScript found on page Critical
3 Prohibited or invalid use of HTML Tag Critical
4 Syntax error Critical
5 Invalid usage of AMP tags Critical

Worse yet, the Google search AMP tester froze when seeing if this page is AMP friendly.

I use a Genesis WP framework that I virtually haven’t altered, so if there is a site that this plugin should work on, it would be mine. However, it doesn’t.

I would be willing to pay for a premium version of this plugin that has support. This plugin’s support requests in the past 5 or so months haven’t been responded to.

I am grateful that the authors of this plugin took the time to make it. However, it concerns me that the WP plugin repository says this plugin (and Yoast’s Glue for AMP plugin) hasn’t been updated in 5 months or so.

Lees alle 110 beoordelingen

Bijdragers & ontwikkelaars

“AMP” is open source software. The following people have contributed to this plugin.

Bijdragers

“AMP” has been translated into these 10 locales: French, Turkish, German, Brazilian Portuguese, Spanish, Italian, Dutch, Chinese (Taiwan), English (UK), English (Australia). Dank voor de vertalers voor hun bijdragen.

Translate “AMP” into your language.

Interested in development?

Browse the code or subscribe to the development log by RSS.

Changelog

0.4.2 (2016-10-13)

  • Fix: Prevent validation errors for html tag (h/t Maxime2 and everyone else that reported this error)
  • Fix: Handle variable name conflict that was causing content_max_width to be ignored (h/t mimancillas)
  • Fix: Prevent errors when nodes don’t have attributes (h/t stephenmax)
  • Fix: Back-compat for 4.5 (add sanitize_hex_color function, h/t xotihcan)
  • Fix: Handle gif featured images (h/t protocolil)
  • Documentation updates (props troyxmccall)

0.4.1 (2016-10-10)

  • Fix: Don’t fire the_content for featured image output
  • Fix: Don’t show comment link when disabled and no comments on post (h/t neotrope)
  • Fix: strip !important from inline styles (h/t compointdesigner and enriccardonagmailcom)

0.4 (2016-10-06)

  • New template: spiffy, shiny, and has the fresh theme smell (props allancole and the Automattic Theme Team).
  • Warning: The template update has potential breaking changes. Please see https://wordpress.org/support/topic/v0-4-whats-new-and-possible-breaking-changes/
  • AMP Customizer: Pick your colours and make the template your own (props DrewAPicture and 10up)
  • Fix: support for inline styles (props coreymckrill).
  • Fix: no more fatal errors when tags not supported by post type (props david-binda)
  • Fix: no more unnecessary <br> tags.
  • Fix: sanitize children of removed nodes (like empty <a> tags) (props Maxime2).
  • Fix: no more broken YouTube URLs with multiple ?s.
  • Fix: properly handle tel and sms schemes (h/t soundstrategies).
  • Fix: remove amp endpoint on deactivate.
  • New filter: amp_pre_get_permalink if you want a completely custom AMP permalink.

0.3.3 (Aug 18, 2016)

  • Handle many more validation errors (props bcampeau and alleyinteractive).
  • New filter: amp_post_template_dir (props mustafauysal).
  • New template: Nav bar is now it’s own template part (props jdevalk).
  • Better ratio for YouTube embeds.
  • Fix: better timezone handling (props rinatkhaziev).
  • Fix: better handling of non-int dimensions (like 100%).
  • Fix: better handling of empty dimensions.
  • Fix: autoplay is a bool-like value.
  • Fix: breakage when using the query_string hook (h/t mkuplens).
  • Fix: don’t break really large Twitter IDs.
  • Fix: don’t break Instagram shortcodes when using URLs with querystrings.
  • Readme improvements (props nickjohnford, sotayamashita)

0.3.2 (Mar 4, 2016)

  • Jetpack Stats ondersteuning.
  • Better version of Merriweather and use system fonts for sans-serif (props mattmiklic).
  • Move font to stylesheet so it can be more easily overridden (props mattmiklic).
  • Fix: Template loading issues on Windows. (Thanks to everyone who reported this, especially w33zy for pointing out the validate_file issue.)
  • Fix: don’t run AMP on post comment feeds (props kraftbj).
  • Fix: un-break pagination when using a static home page with multiple pages.
  • Fix: force amp-iframe to use https to validate correctly (props mister-ben).
  • Fix: validation for target and video/audio attributes.
  • Fix: clipped images in galleries (thanks tobaco).

0.3.1 (Feb 24, 2016)

  • Allow custom query var (props vaurdan).
  • Fix AMP URLs for non-pretty permalinks (props rakuishi).
  • Fix for password-protected posts.
  • Fix dimension extraction for schema-less or relative image URLs.
  • Better fallback for images with no dimensions.
  • Validation fixes for a tags (props kraftbj).
  • Updated AMP boilerplate.
  • Allow on tags for elements (props Steven Evatt).
  • Prefixed class names.

0.3 (Feb 18, 2016)

  • Fetch dimensions for hotlinked images.
  • Ondersteuning voor amp-facebook toegevoegd.
  • Add some new actions and filters (e.g. amp_init).
  • Fix validation errors for [gallery] shortcodes.
  • Fix issues with path validation on Windows.
  • Fix issues with really squeezed layout.
  • Breaking change: style.css no longer contains the ` tag. If you have a custom stylesheet, you need to update it to remove the tag.
  • Breaking change: single.php no longer includes the AMP boilerplate styles. They are instead added via the amp_post_template_head hook. If you have a custom template, please remove the boilerplate styles.

0.2 (Jan 28, 2016)

  • Lots and lots and lots of compatibility and validation fixes
  • Lots and lots and lots of improvements for customization

0.1

  • Initiële versie