🇺🇸United States @alexi721

Artem, thank you very much for uploading your video. At around 4:11 I see a new revision was created under Revisions tab.

Anyway, I added my screen recording ' Screen Recording 2024-06-02 at 8.39.40 PM.mov → ' and here are some comments:
0:07 - Proof that 'page' content type has the 'Create new revision' checkbox marked.
0:21 - Last revision was created on 6/1/24 at 17:43
0:30 - Editing the 'Section Title' field
0:37 - Section Title is changed on frontend
0:50 - Last revision is still set to 6/1/24 at 17:43

Are you sure on your end was no other functionality added i.e. via the ECA module?

At 4:11 of your video the revision log message is 'Shorten text'. Where is this text coming from?
Maybe it was created with a 'rule' via ECA or another script?

Thanks again for your continued support,
Alex

Artem, thank you very much for your detailed reply, which is much appreciated.

A very common use case for site editors is that they need to make a few text changes on pages that have been created by others.
The majority of pages are built with various Paragraphs and the 'Frontend Editing' module allows editors to make those changes without having to open the page in Edit mode.

Unfortunately, even with the 'Create a new revision' checkbox checked on the node level, saving content changes (as shown above) of a Paragraph types using the 'Frontend Editing' module won't create a new revision.

Let me know if you need any additional clarification. Thank you so much.

alexi721 → created an issue.

alexi721 → created an issue.

After upgrading from D9.5.10 to D10.1.2 and to Fontawesome 8.x-2.26 I get the exact same errors as RobbM including the first half of the inserted tags.

Also get the following Javascript error:

fontawesome.min.js?v=6.4.2:6 Uncaught DOMException: Failed to execute 'setAttribute' on 'Element': 'ui-autocomplete-field-term"' is not a valid attribute name.
    at https://sfhsa-d10.ddev.site/libraries/fontawesome/js/fontawesome.min.js?v=6.4.2:6:37822
    at Array.forEach (<anonymous>)
    at a (https://sfhsa-d10.ddev.site/libraries/fontawesome/js/fontawesome.min.js?v=6.4.2:6:37800)
    at https://sfhsa-d10.ddev.site/libraries/fontawesome/js/fontawesome.min.js?v=6.4.2:6:37926
    at Array.forEach (<anonymous>)
    at replace (https://sfhsa-d10.ddev.site/libraries/fontawesome/js/fontawesome.min.js?v=6.4.2:6:37553)
    at Array.map (<anonymous>)
    at https://sfhsa-d10.ddev.site/libraries/fontawesome/js/fontawesome.min.js?v=6.4.2:6:38841

Interestingly, when I enter 'files' all the icons listed when entered just 'file' suddenly appear.

Erich, thank you so much for providing a detailed example on how to get the front-end templates activated in the edit form generated by the 'Layout Paragraphs' module. This is very helpful and worked great.

To make it even better I also imported the styles from the front-end theme by adding the following function to the .module file:

<?php
function admin_template_overrides_form_alter(&$form, FormStateInterface $form_state, $form_id) {
  switch ($form_id) {
    case 'node_page_edit_form':
      // attach the library from the frontend theme
      $form['#attached']['library'][] = '<uswds_base_subtheme>/global';
      break;
  }
}

The only drawback is that the fonts of the Gin theme get overwritten by the fonts of the front-end theme.

@SoCalErich, did you come up with a way to avoid the font replacement of the Gin theme?

Thanks again for sharing your insights with the community.