AMPXF - AMP for Xenforo 2

AMPXF - AMP for Xenforo 2 [Paid] 2.3.0 Patch Level 3

No permission to buy (€50.00)
I fix about 10 urls a day. It's not the plugin's fault... old board code was not good at stripping links. I changed from IPB to vb to xf so there's some legacy stuff in the mix too.

I recommend fixing them if you can.

Assign some work to your moderators to fix.

most of the time it's been bad urls from typos and javascript://style urls that aren't amp compatible.
 
Now that you raised this question, I'm considering that we could actually sell the "Small license" for forums that don't run ads, even if they are over the 5000 daily visitor limit.
This seems like a key feature for larger sites. Focus on them first.
 
Yes, that option is mostly for some old forum that has previosuly been vb and the content has a bunch of <font style="yada yada"> in it that makes the css go over allowed limit..

This is something that another customer saw also and we fixed.

@ThemeHouse maybe can comment on this:

We've noticed that the normal page has the following style set on the <html>-tag:
View attachment 243896
I don't really understand why you would inline a rule that sets font-size to be 62.5% there, unless maybe for some accessibility option?


Anyway the fix that the customer did was to change font size values in ACP to be "px" instead of "rem"

I think the "safer" way to do it would be to edit "amp_style_custom.less" to add the same :
html{font-size:62.5%}
rule.. @ichpen can you add that and report back if font sizes start looking correct?


Yes, this one can be supported, probably without a lot of extra work.


I will likely have a new release out tonight with fixes for various things :)


Seems the biggest issue is postbit, breadcrumbs etc font-sizes getting blown out of proportion. I can CSS them out, will take some time I suspect. Switching to px from rem loses some flexibility with my audience who are likely mostly blind so I prefer not to do that :)
 
Seems the biggest issue is postbit, breadcrumbs etc font-sizes getting blown out of proportion. I can CSS them out, will take some time I suspect. Switching to px from rem loses some flexibility with my audience who are likely mostly blind so I prefer not to do that :)
Did you try the html style fix I mentioned? That one should fix it..
 
First of all, amazing add-on. This is not just an AMP add-on, it is a complete experience :)

Question... The AMP bot is working nicely and found an error with the Content Security Policy. It advises to add a default-src.
I have currently set it as "frame-ancestors 'none'"

Any suggestions about this? I tried adding the recommended AMP CSP, but that seems to break the normal site layout. Probably because it denies too much.

Code:
Header set Content-Security-Policy "default-src * data: blob:; script-src blob: https://cdn.ampproject.org/v0.js https://cdn.ampproject.org/v0/ https://cdn.ampproject.org/viewer/ https://cdn.ampproject.org/rtv/; object-src 'none'; style-src 'unsafe-inline' https://cdn.ampproject.org/rtv/ https://cdn.materialdesignicons.com https://cloud.typography.com https://fast.fonts.net https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://p.typekit.net https://use.fontawesome.com https://use.typekit.net; report-uri https://csp-collector.appspot.com/csp/amp"
 
First of all, amazing add-on. This is not just an AMP add-on, it is a complete experience :)
Thank you! That has kinda been my intention ;)

Any suggestions about this? I tried adding the recommended AMP CSP, but that seems to break the normal site layout. Probably because it denies too much.
Sadly these headers are not my forte, but I know @Masetrix and @briansol where using similar ones at some point, maybe they can advice?

I know the amp-bind docs mention CSP headers here:
1610385472170.webp
 
Hello Mazzly,

Another question, in your website is showing the following message:

1610385606116.webp

This is normal or take some time to your system found my installation?

And i see a lot of people talking about your AMP bot, i have to do something to gain access to it or is automatic and don't need my intervention?
 
Hello Mazzly,

Another question, in your website is showing the following message:

View attachment 243920

This is normal or take some time to your system found my installation?

And i see a lot of people talking about your AMP bot, i have to do something to gain access to it or is automatic and don't need my intervention?
Could you open a support ticket in the ampxf site? then I know which forum it is, and I can advice there :)

The AMPBot has problem getting automatically started for some sites, and I haven't had time to figure it out yet :D
 
for me it appeared after around 12 hours. installed version would appear. you would also get a link to a details page if the bot finds problem with amp pages. i am currently cleaning old email links that were converted into broken href links during one of the conversions. so yeah, you would actually start seeing results after around 12 hours. google search console, incoming hits on amp pages in analytics etc. i see all these changes and it has not been 24 hours yet!
 
I have a question. Say Xenforo down the road builds AMP in their software by default. How would this add-on effect that? I mean say you would uninstall this add-on, would all the existing AMP links indexed remain the same by using the ?amp=1 ? Is this a universal AMP index ending? I wouldn't want to install this now and have Xenforo build it in their software, and then have a bunch of messed up AMP indexed links later on down the road.
 
I have a question. Say Xenforo down the road builds AMP in their software by default. How would this add-on effect that? I mean say you would uninstall this add-on, would all the existing AMP links indexed remain the same by using the ?amp=1 ? Is this a universal AMP index ending? I wouldn't want to install this now and have Xenforo build it in their software, and then have a bunch of messed up AMP indexed links later on down the road.
Well if they enable something like that and use another format, the <meta>-tag on the normal page would start reflecting that, and search engines will update and reindex accordingly.. The important part is that the <meta>-tag

Right away sire. (y)
It should now have noticed the updated version :)
 
However, it is very unlikely that the developers will implement amp in the core now, the request to that effect has been ignored for years.

Should I be wrong, also a simple "redirect 301" in the .htaccess would be enough to redirect the search engines to the right path.
 
Back
Top Bottom