AMPXF - AMP for Xenforo 2

AMPXF - AMP for Xenforo 2 [Paid] 1.4.9

No permission to buy (€50.00)
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
This bot doesn't play well with Imunify360. I've already applied a fix to have the bot allowed, however, looking on the server your site is hosted on, the IP was blocked due to too many captcha requests. I've since moved this to the whitelist.

1613412588235.png

EDIT: Found the blocks, and these happened on this server prior to the fix which I applied on the 7th:

Code:
imunify360-webshield]# zgrep AMPXFBot access.log-202*
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:40:50 +0000] "GET /threads/amprobot.4882?amp=1 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:07 +0000] "GET /amprobot/3dcc3cfa-ae5b-44b5-9ed8-8b9a7ff99c18 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:22 +0000] "GET /amprobot/44faf7d5-b0b3-48f3-bf69-2df13f78d7b8 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:22 +0000] "GET /amprobot/62ce7062-31ef-405b-82b7-868f73dbd669 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:43 +0000] "GET /threads/amprobot.19388?amp=1 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:42:26 +0000] "GET /amprobot/c41bcaf6-3b56-46ed-a838-d7e773d93f8e HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:42:41 +0000] "GET /threads/amprobot.24166?amp=1 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
 
Last edited:
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)?
Currently there is no compatibility for that addon, so I guess AMPXF wouldn't do much with it at the moment at least.

According to the addon page it is using a lot of "standard XF parts", so I guess it could be made compatible with AMPXF quite easily. There were some parts about "autoloading more" that probably won't work tho as AMP has limitations on JS.

Some questions:
Of those people that visit the Portal page, are they coming in through search engines, or are those your "existing users" that come back to consumer the content?
Also: Does that portal page compete/rank well for keywords in the search engines? I'm wondering since the content probably changes quite a bit from day to day?

The benefit of AMP is to increase your search engine rankings for threads, so not having AMP for that single portal page is probably not the whole world. But of course if enough people are using it, and @Jaxel can provide a debug package, I don't see why we couldn't whip up support for it as well :)
 
This bot doesn't play well with Imunify360. I've already applied a fix to have the bot allowed, however, looking on the server your site is hosted on, the IP was blocked due to too many captcha requests. I've since moved this to the whitelist.

View attachment 246407

EDIT: Found the blocks, and these happened on this server prior to the fix which I applied on the 7th:

Code:
imunify360-webshield]# zgrep AMPXFBot access.log-202*
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:40:50 +0000] "GET /threads/amprobot.4882?amp=1 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:07 +0000] "GET /amprobot/3dcc3cfa-ae5b-44b5-9ed8-8b9a7ff99c18 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:22 +0000] "GET /amprobot/44faf7d5-b0b3-48f3-bf69-2df13f78d7b8 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:22 +0000] "GET /amprobot/62ce7062-31ef-405b-82b7-868f73dbd669 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:41:43 +0000] "GET /threads/amprobot.19388?amp=1 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:42:26 +0000] "GET /amprobot/c41bcaf6-3b56-46ed-a838-d7e773d93f8e HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
access.log-20210204.gz:135.181.76.30 - - [03/Feb/2021:19:42:41 +0000] "GET /threads/amprobot.24166?amp=1 HTTP/1.1" 200 20796 site.com "-" "Mozilla/5.0 (compatible; AMPXFBot/1.0; +http://ampxf.com/bot)" WL:"0" "-" XFF:"-" CAPTCHA:"1" PEER:135.181.76.30
Thanks for monitoring this :) 👍
 
The benefit of AMP is to increase your search engine rankings for threads, so not having AMP for that single portal page is probably not the whole world.
Yeah, that makes sense.

So if I understand this right it basically replicates Xenforo threads with a new template? I assume that means that any add-on installed which affects thread templates won't work on mobile devices unless they're specifically supported?
 
Yeah, that makes sense.

So if I understand this right it basically replicates Xenforo threads with a new template? I assume that means that any add-on installed which affects thread templates won't work on mobile devices unless they're specifically supported?
Well it actually uses the same thread template as other addons does, and removes a bunch of stuff that is not according to AMP spec. :) So most things will be the same.

If some addon adds parts to the threads/posts that rely heavily on JS, those won't work well because AMP doesn't support custom JS.. In that case we usually just hide the "non-working" parts for the AMP pages, as they are anyway just a "landing page" for new visitors :)
 
Well it actually uses the same thread template as other addons does, and removes a bunch of stuff that is not according to AMP spec. :) So most things will be the same.

If some addon adds parts to the threads/posts that rely heavily on JS, those won't work well because AMP doesn't support custom JS.. In that case we usually just hide the "non-working" parts for the AMP pages, as they are anyway just a "landing page" for new visitors :)
Thanks for the info! I'm tempted!
 
Hello, i set FA icons on my forum to LIGHT version but on AMP pages FA icons are displayed SOLID, is it possible to fix this ? Thanks. :)
 
Hello, i set FA icons on my forum to LIGHT version but on AMP pages FA icons are displayed SOLID, is it possible to fix this ? Thanks. :)
They are shown as the "regular" and not "solid", this is a limitation with AMP since the FA icons (which is actually a font) needs to be loaded with a <link>-tag, and with AMP that one only allows specific sources, of which one is FA's own CDN.

It should also be possible to load the font "inline" from the XF "local files", but then that whole stylesheet (which is laarge) will count towards the AMP inline style limit, so that quickly becomes problematic instead.

When loading the font from FA sources we can only load the Free version through their CDN, since loading the Pro would require each forum owner to have their own FA Pro license. The limitation with the free version is that it only has the "regular" style, and also much fewer icon (which is fine for our needs)

I would say that if the icons are not a 100% match for first time visitors coming in through google, it doesn't matter much. Once the visitors continues on to your "real site" they will see it exactly as you intended it with light icons :)
 
It seems that even by deactivating the bot it continues to appear online on my forum but constantly crawling an unknown page, is it planned like that?
 
little typo in amp-extra.less
comment line : containter instead container :)
Less:
/* Styling for Ad positions "containter" */
.block-container.block-container-ad {
    width: 100%;
    text-align: center;
    background: transparent;
    border: none;
}
 
little typo in amp-extra.less
containter instead container :)
Less:
/* Styling for Ad positions "containter" */
.block-container.block-container-ad {
    width: 100%;
    text-align: center;
    background: transparent;
    border: none;
}
Oh yeah look at that :D I guess I'll have to fix that for the next release :D
 
My Google Search Console stats went to 2% crawled pages and are now receding slowly but surely. Anyone else seeing this? No errors, and only a couple of warnings. Anything that can be done here.
 
mazzly updated AMPXF - AMP for Xenforo 2 with a new update entry:

1.3.5 Patch Level 3

  • Style property for setting Sidebar colors if they differ
    • Seems some forums running ThemeHouse/UIX need this
  • ThemeHouse font fix further fixed, apparently they do:
    • Set 62.5% font size on html-tag (This we already had fix for)
    • Set body-tag font-size to 1.5rem. (This we didn't have, making some forums font sizes be too small in some parts of messages...)
  • Ensure that "share icons"...

Read the rest of this update entry...
 
My Google Search Console stats went to 2% crawled pages and are now receding slowly but surely. Anyone else seeing this? No errors, and only a couple of warnings. Anything that can be done here.
Is this only AMP pages, or all pages in GSC? 🤔
 
Top Bottom