AMPXF - AMP for Xenforo 2

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

No permission to buy (€50.00)
So does it mean I have to wait until you are back from your holidays to have an answer? I purchased a service! 😳 Unbelievable
No it doesn't, and I gave you some answers already 😊

it simply means that there won't be an answer directly since I am not at the office and in front off the computer 24/7

Aren't you ashamed to take a vacation in the middle of summer??
Here in Finland the July month is the best one to take time off and go out and enjoy the nature 😎

I don't feel ashamed of taking time to recharge my batteries as the alternative would be to not do it and probably have a burnout. (which would mean no support/updates here)
 
I've been encountering several issues with the XenForo AMP add-on related to CSS syntax and nesting in the "style amp-custom" tag. Despite reinstalling the add-on, these errors persist. Here are the details and steps I’ve taken to address these issues:

Issues and Troubleshooting Steps:​

  1. CSS Over-Nesting in "style amp-custom" Tag:
    • Error: The "style amp-custom" tag contains excessively nested CSS rules.
    • Description: AMP pages require CSS to be optimized and free from excessive nesting, which can lead to validation errors.
  2. Allowed Style Tags:
    • Error: Only amp-boilerplate and amp-custom style tags are permitted within the head section of the document.
    • Description: AMP restricts the types of style tags allowed in the head section to ensure fast loading and a streamlined structure.
  3. CSS Syntax Error in "style amp-custom" Tag:
    • Error: Syntax errors in the CSS within the "style amp-custom" tag.
    • Description: These errors indicate invalid CSS rules, making the AMP page invalid according to AMP Validator standards.

Steps to Resolve:​

  1. Review and Optimize CSS Code:
    • Ensure that your CSS code within the amp-custom style tag is not excessively nested. Simplify and flatten the CSS rules where possible.
    • Use tools like CSSLint or AMP Validator to identify and fix syntax errors in your CSS.
  2. Allowed Style Tags Compliance:
    • Verify that only amp-boilerplate and amp-custom style tags are present in the head section of your document. Remove any other style tags that might be causing validation issues.
  3. Update XenForo and AMP Add-on:
    • Make sure you are using the latest versions of both XenForo and the AMP add-on. Updates often include fixes for known issues and improved compliance with AMP standards.

I’ve reached out to AMPXF.com support and submitted a ticket regarding these issues. While waiting for their feedback, I am continuing to optimize the CSS and ensure compliance with AMP standards.

By following these steps, you can address the CSS over-nesting, allowed style tag restrictions, and syntax errors in the "style amp-custom" tag with the XenForo AMP add-on. Optimizing your CSS and adhering to AMP guidelines are critical steps in resolving these issues.

If you have any additional insights or questions, please feel free to share them here. Let’s work together to make our forums faster and more compliant with AMP standards. Happy forum managing!
 
Latest V console warnings.

Code:
An HTML tag contains the same attribute repeated multiple times.


Code:
<amp-img width="22" height="22" layout="fixed" src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)"></amp-img></div>
 
Here are also problems in the console since the last update:

Problems of type “AMP” detected in https://www.***.de/

To the owner of https://www.***.de/:

Search Console has detected that your site is affected by 1 AMP issue(s). The following issues were found on your site. We recommend fixing these issues where possible so that Google Search works optimally and has a wide reach.

Most common non-critical issues:

An HTML tag contains the same attribute multiple times.
No critical issues are suggestions for improvement. They do not prevent a page or feature from appearing in Google search results. Some non-critical issues will negatively impact search appearances, while others may later be promoted to critical issues.
 
I have to say using this plugin has been pretty hit & miss. Google can't make up it's mind.
 

Attachments

  • Screenshot (247).webp
    Screenshot (247).webp
    19.4 KB · Views: 26
Back
Top Bottom