Title: Conflicts with AMP Last modified: November 16, 2017 --- # Conflicts with AMP * Resolved [osseonews](https://wordpress.org/support/users/osseonews/) * (@osseonews) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/) * We use AMP for WP plugin to create an AMP website ([https://wordpress.org/support/plugin/accelerated-mobile-pages/](https://wordpress.org/support/plugin/accelerated-mobile-pages/)). However, on our AMP pages the Foo Galleries are not displayed. Example, regular page: [https://www.osseonews.com/challenge-concavity-implant-site/](https://www.osseonews.com/challenge-concavity-implant-site/) * AMP page: [https://www.osseonews.com/challenge-concavity-implant-site/amp/](https://www.osseonews.com/challenge-concavity-implant-site/amp/) * None of the images show up. Just grey lines. This happened after the latest update. Prior versions seemed to work with AMP. Viewing 7 replies - 1 through 7 (of 7 total) * Thread Starter [osseonews](https://wordpress.org/support/users/osseonews/) * (@osseonews) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9691171) * BTW, I can confirm this is a problem with Foogallery latest version. I rolled back our website to 1.3.8 version and the images show fine. As I don’t have access to any other version, I can’t say when this plugin started to break display of images on AMP websites. Apparently, the code you used to display images has changed which prevents AMP in WordPress from recognizing the images and making them AMP compatible. This is a shame, as AMP is a huge traffic driver to many websites. Will have to just revert back to earlier version of this plugin. If you have a better repository of earlier versions we can test and see which version starts to break the AMP website. * Thread Starter [osseonews](https://wordpress.org/support/users/osseonews/) * (@osseonews) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9691231) * I was looking at the code and apparently, the entire HTML output for displaying images has changed, so now for example instead of using SRC attribute to show an image, you use: data-src-fg in the img tag. Not sure why you changed the code, but nevertheless my guess is that AMP has no clue this is an image because you don’t have the attributes they are looking for in this tag. * Plugin Author [steveush](https://wordpress.org/support/users/steveush/) * (@steveush) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9693722) * Hi, * Sorry but this is not something we test for or support out of the box. AMP support would require a number of changes to the way the CSS, JS and HTML is output. As can be seen in your example page, AMP pages don’t include the FooGallery JS and CSS files due to restrictions. Also if you take a look at the changelog for [https://wordpress.org/plugins/accelerated-mobile-pages/](https://wordpress.org/plugins/accelerated-mobile-pages/) you can see they are having to build in support for AMP into popular plugins, and charging a premium for it. * As for the images they no longer use the src attribute as they get loaded by the JS, which is not being loaded into your page. Previously I think it used to “work” for you as it did as you say output the old img tag with a src attribute however seeing as there is no CSS or JS for FooGallery being included in the page that was all you were really getting, the raw HTML with no styling or layout. * We will look at and discuss the possibility of basic AMP support but it would not be able to support the current available feature set of FooGallery due to the limitations placed on page content by AMP itself. * Regards * Thread Starter [osseonews](https://wordpress.org/support/users/osseonews/) * (@osseonews) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9693771) * Thanks for the reply. I appreciate your hard work. * Howver, Google AMP is probably one of the most important developments in websites in years. Since the majority of web users navigate the web via mobile now, ignoring Google AMP is basically a recipe for failure of any website business. I highly recommend you develop your plugin to be compatible with Google AMP and the core plugin ([https://wordpress.org/plugins/amp/](https://wordpress.org/plugins/amp/)) that converts WordPress sites to AMP. This plugin is actually maintained by Automatic, the owners of WordPress, which should show you how vital AMP is to the future of the Web. If Foogallery is not compatible with AMP it will be useless quite soon for the vast majority of users. * Incidentally, we downgraded our Foogallery back to 1.3.8 now, because that version works very well and is compatible with AMP. - This reply was modified 8 years, 9 months ago by [osseonews](https://wordpress.org/support/users/osseonews/). * Thread Starter [osseonews](https://wordpress.org/support/users/osseonews/) * (@osseonews) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9693802) * BTW, in terms of this: “As for the images they no longer use the src attribute as they get loaded by the JS”. IMHO, this is a poor coding choice for many reasons, but particularly given the fact that it makes your plugin completely incompatible with Google AMP (even the Automatic plugin). What your coders should do is simply have a checkbox that uses the old code for displaying an image using the SRC attribute, for those who want Google AMP compatibility (which will be every single serious web business very shortly) - This reply was modified 8 years, 9 months ago by [osseonews](https://wordpress.org/support/users/osseonews/). * [Adam W. Warner](https://wordpress.org/support/users/awarner20/) * (@awarner20) * [8 years, 9 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9694401) * Hi [@osseonews](https://wordpress.org/support/users/osseonews/), * We are currently looking deeper into supporting AMP and we appreciate you bringing it to our attention. We realize the trend of AMP usage will only rise and will do what we can to come up with a solution. * [Adam W. Warner](https://wordpress.org/support/users/awarner20/) * (@awarner20) * [8 years, 8 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9705825) * Continuing to evaluate an AMP solution internally. Marking as resolved for now. Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘Conflicts with AMP’ is closed to new replies. * ![](https://ps.w.org/foogallery/assets/icon-256x256.gif?rev=2602542) * [Photo Gallery by FooGallery : Responsive Image Gallery, Masonry Gallery & Carousel](https://wordpress.org/plugins/foogallery/) * [Frequently Asked Questions](https://wordpress.org/plugins/foogallery/#faq) * [Support Threads](https://wordpress.org/support/plugin/foogallery/) * [Active Topics](https://wordpress.org/support/plugin/foogallery/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/foogallery/unresolved/) * [Reviews](https://wordpress.org/support/plugin/foogallery/reviews/) * 7 replies * 3 participants * Last reply from: [Adam W. Warner](https://wordpress.org/support/users/awarner20/) * Last activity: [8 years, 8 months ago](https://wordpress.org/support/topic/conflicts-with-amp-2/#post-9705825) * Status: resolved