I’ve identified that the AssertionError no longer occurs and saving works as expected when following these steps:
- Drag the Styles button to the active toolbar.
- Immediately afterwards, define the classes in the Styles textarea (do not leave it empty).
- Wait for 1 to 2 minutes.
- After that period, proceed to save.
I'm using DDEV, Drupal 10.3.7.
However, another issue remains: the Styles dropdown in CKEditor does not display any available classes (screenshot attached for reference).
Closed
Merge request done!
The logo proposal is approved.
Corrected indentation in twig file.
Created tag v.1.0.4.
I have implemented the requested changes:
- Adjusted the array formatting to comply with the 80-character limit.
- Updated the whatsapp_button.info.yml package from "Custom" to "Social Media."
- Revised the docblock in whatsapp_button.module to follow Drupal standards.
- Removed the outdated whatsapp_button_preprocess_block function.
- Added an initial README.md file with basic module documentation.
The updated code has been committed under tag 1.0.2.
Additionally, I have verified that Git is set to use the same email associated with my Drupal.org account.
Please review and let me know if any further adjustments are needed.
ricardo.castaneda → created an issue.
santiagon → credited ricardo.castaneda → .
Hola, propongo el tema de las Core Web Vitals (CWV), el cual está comprendido por las métricas: Interaction to Next Paint (INP), Cumulative Layout Shift (CLS) y Largest Contentful Paint (LCP). Las CWV son como la salud de un sitio web, puesto que su correcta implementación favorece la experiencia de los usuarios y el rendimiento. Por otro lado, un sitio con buen rendimiento es un sitio veloz que es accesible para usuarios con conexiones lentas.
Asimismo, propongo el tema del Content Overrides, que forma parte de las herramientas de desarrollo de Chrome. Con el Content Overrides desde un entorno local se pueden realizar cambios persistentes en el HTML de un sitio web en producción.