Problem/Motivation
Due to ajax calls on node edit form, Acquia Optimize not functioning properly and went into ajax chaining
Steps to reproduce
Proposed resolution
Re-structure into Modal form.
User interface changes
- Content pages now feature a modal-based Quick Scan functionality, similar to the extension-based version.
- SVG files are now served from the images folder.
- Each section—SEO, Accessibility, Data Privacy, and Readability—has its own Twig section.
API changes
- A new route, '/acquia-optimize/api/content-quick-scan/{scan-id}', has been introduced to handle scan results rendering in Twig templates.
- Scan result data processing is now centralized for both extension and content pages.
New implementation and updates:
- Readability now uses the LIX metric.
- ENUMS have been introduced for managing SEO issues and readability metrics.
- The minimum supported version of Drupal has been updated to 10.3.
- Polling for content pages is now handled at server-side.
- Quick Scan can now run on new nodes, with pre-validation to ensure required fields are filled before execution.
Issue fork acquia_optimize-3538217
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
ankitv18 commentedMR!23 is ready for a review.
Comment #10
vishalkhode commented@ankitv18: Merged the MR. Awesome work on this. We've made a significant change, we can add all those details in the ticket as well ? Then, will mark this ticket as fixed. Thanks.
Comment #12
ankitv18 commentedComment #13
ankitv18 commentedComment #14
ankitv18 commentedComment #15
ankitv18 commentedComment #19
vishalkhode commentedComment #20
vishalkhode commented