kscott29

any update on this? FYI this is beyond Cloudflare. To me it appears like a Siteground issue itself. I removed SG Optimizer, changed CDN providers to Stackpath and as soon as I switched my A record over to Stackpath’s IP it started doing the same thing.

Worth noting that if you use the subdomain approach to serve CDN assets it works just fine..

@ahmedkaludi I contacted you two days ago via the contact us page that you posted in the github link but I haven’t heard any responses. How can I fix these 500 errors?

I added a new bug in github:

https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/3183

I prefer not to publish my domain urls on this forum, which is why I’ve always used shorteners in the past.
@ahmedkaludi you can check the url: https://www.caraudionow.com/common-car-stereo-problems/amp/ or https://www.caraudionow.com/car-speakers-why-they-blow/amp/

Here’s the error:

Fatal error: Uncaught Error: Class 'AMPforWP\AMPVendor\WP_Error' not found in /home/123/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/sanitizers/class-amp-style-sanitizer.php:259 Stack trace: #0 /home/123/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/sanitizers/class-amp-style-sanitizer.php(339): AMPforWP\AMPVendor\AMP_Style_Sanitizer->get_validated_css_file_path('https://compone...') #1 /home/123/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/sanitizers/class-amp-style-sanitizer.php(192): AMPforWP\AMPVendor\AMP_Style_Sanitizer->process_link_element(Object(DOMElement)) #2 /home/123/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-content.php(129): AMPforWP\AMPVendor\AMP_Style_Sanitizer->sanitize() #3 /home/123/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-content.php(94): AMPforWP\AMPVendor in /home/123/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/sanitizers/class-amp-style-sanitizer.php on line 259

• This reply was modified 5 years, 10 months ago by kscott29.

Thanks, I enabled the custom home page, however it seems like there are still some bugs in the amp page builder. None of my text or settings save when I’m using the page builder. Every time I hit “Update” the information in my page builder modules is wiped clean.

Hi @ampforwp. I’ve sent an email to your team but have not received a response. Can you confirm you’ve received it? Thanks!

Any recommendations on how? I’m no developer, but I can find and replace ??

Thanks for the reply! At the moment, in order to get amp pages to show up I need to copy paste the entire markup from the View Source of the page, then paste it into the text editor of the post.

In my case, the page builder does not reside on the post editor. It has its own editor that you need to engage with separate of the post editor in order to build the page.

Would I be able to engage with you and your team to build a custom solution for my use case and theme?

Much appreciated!

Ahmed,

I found that there is a conflict with another plugin that just started: https://www.ads-software.com/plugins/seo-internal-links/

It doesn’t look like there’s been any updates to this plugin lately though. After I de-activated this plugin, AMP pages began working again. Can you see if there’s something that was changed in your plugin or the AMP plugin that may have conflicted with this plugin in recent updates?

Hi Ahmed,

Thanks for the quick reply. I currently use a page builder that’s build into my theme to display the mobile and desktop version of my posts. However, I take the content from the page builder and add it into the standard post area, which is what will show up in the AMP pages normally.

It did work originally and stopped recently. I’m not sure the exact date when it stopped though. Even if I select to use the custom AMP content in the post editor it doesn’t appear.

No, unfortunately this didn’t fix the problem :/

Anyone? I still can’t figure it out!

Anyone?

@gary Cao, @gfhs mentioned a few days ago that this line of code doesn’t have an effect, I’m having the same issue.

I copied and added the define( ‘WPSC_CUSTOMER_DATA_EXPIRATION’, 3.5 * 3600 ); to my wp-config.php file and changed the “3.5” to “3” hours and it has had no effect. It’s been 5 hours since I implemented the change. Still manually deleting users.