acquia_optimize 1.3.0

This release updates for the Acquia Optimize module to include several enhancements, bug fixes & performance issues. Notable features added are the ability to retry scans on failure and the display of readability level and data privacy in scan results. The Acquia Optimize Scan functionality has been extended to new content nodes, with a Quick Scan button now available on content add/edit forms. Bug fixes address issues such as tooltip visibility on the XB extension and multiple API calls when the Quick Scan button is clicked. Additionally, the CI pipeline now supports the previous major version of Drupal.

Contributors (2)

ankitv18, vishalkhode

Issues: 10 issues resolved.

Changelog

Changes since 1.2.2 (compare):

🚀 Task:

• #3538291: Add 2 retries when the scan fails on the XB extension.
• #3538826: Scan results containing Readability Level and Data Privacy is also now shown to the user.
• #3538217:
  • The Acquia Optimize Scan functionality now works on new content nodes, not just on node edit pages.
  • The Acquia Optimize - Quick Scan button appears on Content Add/Edit forms. When clicked, it opens a modal where users can start Scanning the Content page and/or navigate to links such as Configure API settings and Optimize account.
  • The minimum supported version of Drupal Core is now 10.3.

🐛 Bug:

• #3540155: The tooltip was cut off on the XB extension on Configure API settings form.
• #3541180: When the Quick Scan button is clicked on the XB extension, an API call to fetch settings is made multiple times.
• #3541212: Readability sections now display the results as per LIX metrics.

Misc:

• #3539932: The CI pipeline now runs on the previous major version of Drupal as well, specifically Drupal Core 10.x.
• #3525988: Add return types to missing methods of SettingsForm.
• #3536086: The Validate pipline is now fixed.
• #3542849: The disclaimer under Readability section is now updated as per LIX readability index.