AMPXF - AMP for Xenforo 2

AMPXF - AMP for Xenforo 2 [Paid] 1.4.9

No permission to buy (€50.00)
I have a request, or rather a question -

Really happy so far. On my tests, everything is super fast.

I use an addon to display articles on my front page by @Lawrence called - Thread Preview Widget

This is the result when an AMP URL is added -


View attachment 246366

If this is what my users see when they find my site front page, instead of the threads or forum - then I think they'll be very unimpressed :(

Any idea of a fix or solution?

Thank you! :) Looking forward for great stuff to come.
There are very likely some missing styling there, I will have a fix out later today
I also found another bug -

View attachment 246367

When I highlight this, it's the text below the image -

View attachment 246368


Thank you
Same thing here, please open a support ticket for this and I can instruct you the "workaround" for this one until it is fixed in release later today :)
for that :) 👍
 
Questions about the bot:
  • Why does the bot keep crawling our sites ? I see it has crawled 10,000 pages now, no errors were found. So can we assume that if I don't make any HTML / CSS / JS modifications on my site it won't find any?
  • Does the bot need to crawl all threads to become AMP?
If the answers to these two questions are YES and NO can't we have an option to pause the robot on its site? Or it's not necessary ?
 
Questions about the bot:
  • Why does the bot keep crawling our sites ? I see it has crawled 10,000 pages now, no errors were found. So can we assume that if I don't make any HTML / CSS / JS modifications on my site it won't find any?
  • Does the bot need to crawl all threads to become AMP?
If the answers to these two questions are YES and NO can't we have an option to pause the robot on its site? Or it's not necessary ?
Yes if no need to run you can pause the bot also 👍

We yesterday added a button for that specific purpose 😊
 
I've got the 404 not found add-on installed and I am getting quite a lot of errors about a certain 404:

https://www.motor-forum.nl/amp-pixel/<<id>>
Referrer:
https://www-my--domain-copm.cdn.ampproject.org/v/s/www.my-domain.com/threads/dikke-vette-krassen-op-mijn-tank.202985/?amp=1&amp_js_v=0.1&usqp=mq331AQHKAFQArABIA%3D%3D

Or

https://www.my-domain.com/amp-pixel/<<id>>
Referrer:
https://www-my--domain-com.cdn.ampproject.org/
 
I've got the 404 not found add-on installed and I am getting quite a lot of errors about a certain 404:

https://www.motor-forum.nl/amp-pixel/<<id>>
Referrer:
https://www-my--domain-copm.cdn.ampproject.org/v/s/www.my-domain.com/threads/dikke-vette-krassen-op-mijn-tank.202985/?amp=1&amp_js_v=0.1&usqp=mq331AQHKAFQArABIA%3D%3D

Or

https://www.my-domain.com/amp-pixel/<<id>>
Referrer:
https://www-my--domain-com.cdn.ampproject.org/


 
I might be completely wrong because I know nothing about it... )
but I do have like 200+ of those records too. what I noticed that if I check those pages with GSpeedInsights it shows a warning: use modern img formats. Unable to decode /threads/title.xxx/?amp-pixel=1

It looks like we need webp support.
 
but I do have like 200+ of those records too
Those were temporary when going from 1.3.4 to newer version :)
what I noticed that if I check those pages with GSpeedInsights it shows a warning: use modern img formats. Unable to decode /threads/title.xxx/?amp-pixel=1
Yes, the amp-pixel is not really a "real" image so if it tries to load it as such it will fail. the <amp-pixel> doesn't care about it not being valid as it is never really "loaded", only thing that matters is that the content-type is correct image/X
It looks like we need webp support.
When AMP pages are served throught the AMP caches they will be webp if the mobile browser supports it. Most do (even Safari nowadays)
By the way, do we have other options to serve imgs in webp except paying cloudflare $20 monthly?
It is also possible with the PageSpeed module for Nginx/Apache, but I don't recommend installing that unless you want to fiddle with server-related things :)
Don't know, I use the $20 CF plan for that.

You can take a look at this add-on for image size reduction: https://xenforo.com/community/resources/th-image-optimizer.5723/

Reduced total size from from 530gb to 240gb on our forum.
I use a similar addon that does the same thing:
@mazzly Font Awesome Bookmark Icons broken in post number.

View attachment 246380

Also Please add support for @AddonsLab Original Poster Highlight addon. Thread starter icons does not showing correctly.

View attachment 246381
I'll look into it for todays release 👍

Could you please start putting things you find into support tickets on ampxf? They so easily drown away here between the posts :)
 
Those were temporary when going from 1.3.4 to newer version :)

Yes, the amp-pixel is not really a "real" image so if it tries to load it as such it will fail. the <amp-pixel> doesn't care about it not being valid as it is never really "loaded", only thing that matters is that the content-type is correct image/X

When AMP pages are served throught the AMP caches they will be webp if the mobile browser supports it. Most do (even Safari nowadays)

It is also possible with the PageSpeed module for Nginx/Apache, but I don't recommend installing that unless you want to fiddle with server-related things :)

I use a similar addon that does the same thing:

I'll look into it for todays release 👍

Could you please start putting things you find into support tickets on ampxf? They so easily drown away here between the posts :)
My bad, I also use that optimizer haha. Local processing of images so a lot cheaper.
 
I got an email (Subject: The AMPbot has been paused) saying:

Please fix the problems shown on ampxf.com and restart it

But there were no problems to fix.

So I restarted it. Any reason why I would get this message?

Thanks
 
I got an email (Subject: The AMPbot has been paused) saying:

Please fix the problems shown on ampxf.com and restart it

But there were no problems to fix.

So I restarted it. Any reason why I would get this message?

Thanks
If the bot is being blocked it might also happed.. need to fix the message a bit better.. Please open a support ticket on ampxf :)
 
There are very likely some missing styling there, I will have a fix out later today

Same thing here, please open a support ticket for this and I can instruct you the "workaround" for this one until it is fixed in release later today :)
for that :) 👍
I've just opened 3 support tickets. Thank you :)

1613400542834.webp
 
@mazzly What this error Referenced AMP URL is not an AMP?

View attachment 246394
This can happen if you e.g. have the addon disabled for a while and the googlebot visits at that time.

It can also happen if e.g. the googlebot visits a page exactly when you are updating (as the AMP page doesn't render for a few seconds during update).

Are there many pages like this?

You should probably check if the pages they list are working as AMP or not. If working fine, simply click the "validate fix" button:
1613406202207.webp

But my initial hunch is that the googlebot is showing false-positives (like it usually does..). This is one of the reason the AMPBot is much better for fixing problems, it won't lie to you :)
 
Hmmm. Interesting! I have a biggish site (30K+ visitors per day), so I'm in the £250 bracket.

I use XenPorta as my front page, which is the most viewed page on the site. How would this interact with that (if at all)?
 
Top Bottom