aglyons

That would make sense however, disabling autoptimize allows the Divi builder to load properly.

tried that. made no difference.

I should add. This behavior only started following the last Divi update to support WP5.

It’s their latest editor version.

I also have noticed that it won’t replace images defined in CSS

Hey Cody,

Thanks for the answer.

I have another question that I’ll post separately.

Hi Cody,

I noticed the thread that mentioned that. It is building, but, it’s building pretty slowly. How is the cache built up? I’ve gone through each page while logged out and the cache was saying there was about 200kb in it. Going through 6 pages on the site, you would think there would be more than 200kb cached.

Btw, I bought the optimus HQ license so images are getting converted to webp. Does that introduce a noticable delay in building the cache pages, both regular and compressed?

Hmmm, I’ve installed and refreshed my page multiple times with a full local cache clear (Chrome dev) and it’s still showing “Current cache size: Empty”

Cache expiry is set to 0. All cache behaviors are unchecked. I have no exclusions and minification is turned off as I am using Autoptimize.

Good thing there is a new fully fledged API available for Divi.

The odd thing is, it’s there in the code. The containing DIV gets collapsed for some reason.

Hey Marqas,

OK, I think the solution was the permalinks thing. I refreshed the permalink and the homepage started showing.

BUT, now there’s another problem popping up. There are no pictures showing. At first, I thought is was because I’m defining the images as background images for a DIV. So I rebuilt a special page for the AMP homepage and set the page in the settings page to show it. The weird thing is if you look at the page I created to be the new home using the page’s direct URL, the pictures show. If you view just the homepage, the pictures don’t show.

clients.torontoheadshot.com/home-amp/amp/

vs

clients.torontoheadshot.com/amp/

It’s the same page but when the redirect is in place, the pictures don’t show.

I am seeing the exact same issue.

I am in the process of rebuilding my WP site by hand and have a clean installation going which is scoring 94 on page speed for the desktop version.

The AMP version is showing the blogroll issue described above. I haven’t done any special redirects or anything, just the standard WP homepage settings under reading. All the AMP settings are default at this point.

the rebuilt site is clients.torontoheadshot.com

FYI, I am using Elegant Themes Divi theme on the site. I was following this article (https://ampforwp.com/enable-amp-on-wp-divi-theme/) on enabling AMP specifically for Divi sites. There doesn’t seem to be anything special that needs to be done in order for Divi to work with AMPforWP.

I’m getting this error as well.

WP:4.8
AMP for WP: 0.9.53
AMP (Automatic): 0.4.2

PHP Warning: fopen(): https:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/torontoheadshot/public_html/wp-content/plugins/amp/includes/lib/class-fastimage.php on line 31

Looking into fopen() PHP directive states that it could be used to inject malicious code. That being the case, I don’t feel comfortable enabling that on php.ini on a live server.

Same problem here. It’s concerning that this post has been up for months and there’s been no response from dev.

Thanks @bcworkz, I’m pretty much a noobie here, where would I go to look for tickets or file a new one?

EDIT -Never mind, just saw your link, DUH

• This reply was modified 7 years, 12 months ago by aglyons.

Same issue here but more of them. Not sure who should be looking at this. The AMP plugin team or the theme developers.

As reported by Search Console

AMP markup missing or incorrect

The property ‘minimum-scale’ is missing from attribute ‘content’ in tag ‘meta name=viewport’.
The mandatory text (CDATA) inside tag ‘head > style[amp-boilerplate] – old variant’ is missing or incorrect.

Prohibited HTML Tag with AMP equivalent

The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?

Prohibited or invalid use of HTML Tag

Invalid URL protocol ‘http:’ for attribute ‘src’ in tag ‘img’.
The parent tag of tag ‘noscript > style[amp-boilerplate] – old variant’ is ‘head’, but it can only be ‘noscript’.
The attribute ‘onclick’ may not appear in tag ‘a’.
The mandatory attribute ‘amp-custom’ is missing in tag ‘style amp-custom’.

Info: Missing structured data element

Invalid CSS stylesheet

The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value

User-authored JavaScript found on page

The tag ‘script’ is disallowed except in specific forms.