• Home
  • Get help
  • Ask a question

#89 – AMP development version and production version are distinct

Posted in ‘weeblrAMP’
This is a public ticket. Everybody will be able to see its contents. Only enter usernames, passwords or any other sensitive information in the Private information field.
Friday, 25 May 2018 22:59 UTC
hugovandrunen
 I adapted some pages on a production site, validated AMP and changed operation mode to normal.

Now I have two versions of the same Amp page:
V1: on the amp url without final slash .../amp I have the page I designed during development operation mode
V2: on the same page with final slash .../amp/ I have a reduced version equal to the version in the Google Amp cache.

It's is posible to see in the browser the html of both versions.

V1 maintains a lot of divs with the original css classes, which allows a nice design, close to the no-amp version, see the buttons. But is V1 AMP? Does it comply with AMP rules? This is the version I see during development with WeeblrAmp, it makes me happy.

V2 has less divs, changes divs for ps, etc. I suppose it complies with AMP rules. But it's reduduced in presentation and in content. I loose a lot of my original page. It's the page my mobile visitors see. Most visitors are mobile. V2 is not the page I want them to see. So I shut down Adwords for the moment. V2 also has the breaktags, see ticket 85.

I have invested quite some time to make this work. If something like V1 is what I can obtain with AMP then it may be worth the effort, if V2 is what AMP can give, then I will not use it on my sites, the display of normal pages on mobile I have is much better. That's the decision I have to make.

Do you think you can do something about it?

You can see this behavior on a production site. I copied also content to the test site where you can play around and make changes. But the problem V2 does not show there yet, may be because Google hasn't seen it yet, it's in development operation mode.


Kind regards
Monday, 28 May 2018 08:32 UTC
wb_weeblrpress
Hi

The Google AMP cache is not relavant here, it actually has versions of both pages, that's just a cache.
See:
https://suite-quito-viajes.cdn.ampproject.org/c/suite.xxxxx.viajes/suite-xxxxx/dos-yyyyy/amp

and
https://suite-quito-viajes.cdn.ampproject.org/c/suite.xxxxx.viajes/suite-xxxxx/dos-yyyyy/amp

I don't see how what you describe about having 2 URLS would be an issue. If I visit:

suite.xxxxx.viajes/suite-xxxxx/dos-yyyyy (without trailing slash)

I get redirected to

suite.xxxxx.viajes/suite-xxxxx/dos-yyyyy/ (with a trailing slash)

which means that the page without a trailing slash is not going to be indexed and thus the corresponding AMP page will not be indexed or used either.

Now the real problem would be those missing images in the second version of the page.

I can't say why they are missing on the second version. I can't imagine weeblrAMP removing them from one page and not from the other. So that would indicate that the page builder does not add them in the source code in the second case. Maybe it'd be interesting to know how they are inserted? just regular content in the original source? or within specific AMP tags?

The rest of the page seems good, so what's special about those buttons and image?

Best regards
 
Tuesday, 29 May 2018 16:01 UTC
hugovandrunen
Hi

There are really two versions.

I tried with different browsers, laptops and internet providers. And with https://tools.pingdom.com/
So it´s important you get to see and compare the two versions.

The difference is a entirely distinct html.

V1 has (almost) all original divs with pagebuilder classes. V1 is quite stripped down. Certain images and elements not showing in V2 is a consequence of the html.

Best regards
Tuesday, 29 May 2018 16:13 UTC
wb_weeblrpress
Hi

I can see now that the second page is basically one where BeaverBuilder has not replaced the content. It's just the raw post data.

I have not noticed that when I worked on the copy of your site. I'll try see if this can be reproduced and understood.

Best regards


 
Tuesday, 29 May 2018 16:25 UTC
wb_weeblrpress
Hi

I am a bit confused now. I tested on my local copy but could not reproduce the problem. So I tested with your own site, on the pages available there:

https://testsite.net/bb/furnished/two-bedrooms/amp/
and
https://testsite.net/bb/furnished/two-bedrooms/amp

and the problem does not appear. Both pages are displayed fine, altough of course only the first one is actually available on the site, I have to manually remove the trailing slash to see the other.

Best regards

 
Monday, 04 June 2018 16:00 UTC
hugovandrunen
Hi

I found the problem, at last.

On weeblrAMP Settings - Comments and plugins - Plugins management - Disable on AMP pages:

Beaver Builder Plugin should not be checked. That is: the page builder should not be disabled.


The problem may happen when BB is disabled, because without BB active AMP is taken from the normal WP page which has some common elements of the BB page (text, simple images) but lacks other special element like galleries. Also this behavior seems not very consistent, see the difference with and without trailing slash.


Best regards
Monday, 04 June 2018 16:10 UTC
wb_weeblrpress
Hi

Beaver Builder Plugin should not be checked. That is: the page builder should not be disabled.
Yes, sorry for not thinking about it before, that makes totall sense: if BeaverBuilder is disabled, it just won't process the content and you're stuck with the post content.

Also this behavior seems not very consistent, see the difference with and without trailing slash.
Actually, I think I understand now: to be able to disable plugins, we use a MU plugin, that runs before anything else in WordPress (you have to run first, to be able to disable other plugins).
In the plugin, we do not have all the power of WordPress to check whether a page is AMP or not so we rely on a rather crude method of detecting the "amp" suffix at the end of the requested URL.

When requesting the xxxx/amp URL, the suffix was detected and the BeaverBuilder plugin was disabled.
When requesting the xxxx/amp/ URL, the suffix was NOT detected - because of the trailing slash - and the BeaverBuilder plugin was NOT disabled.

As BB was not disabled, the page was rendered as expected. There is no inconsistencies here, the root of the issue is indeed that the BB plugin was marked as disabled on AMP pages. The inconsistency was only a result of the limit imposed by WP on our abilities to disable other plugins.

Best regards

 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.