Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edit Contentlet: Add TinyMCE V6 WYSIWFY field to the form #27943

Closed
2 tasks
Tracked by #25445
rjvelazco opened this issue Mar 12, 2024 · 4 comments · Fixed by #27961
Closed
2 tasks
Tracked by #25445

Edit Contentlet: Add TinyMCE V6 WYSIWFY field to the form #27943

rjvelazco opened this issue Mar 12, 2024 · 4 comments · Fixed by #27961

Comments

@rjvelazco
Copy link
Contributor

rjvelazco commented Mar 12, 2024

Parent Issue

#25445

Task

Implement the TinyMCE V6 to add the WYSIWFY field to the form.

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

Acceptance Criteria

  • All plugins available on the old WYSIWYG field should work on the new field.
  • The user should not lose the content when updating it to the new one.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

Here is the list of plugins that are supported in the TinyMCE v6: #27519 (comment)

Assumptions & Initiation Needs

Docs:

  1. Install TinyMCE V6 in Angular (MIT License)
  2. Plugins

Quality Assurance Notes & Workarounds

The custom plugins that were developed in dotCMS for TinyMCE will be migrated to Angular in a separate ticket.

Sub-Tasks & Estimates

No response

@rjvelazco rjvelazco added OKR : Core Features Owned by Will and removed OKR : User Experience Owned by Jason labels Mar 12, 2024
@rjvelazco rjvelazco changed the title Edit Contentlet: Add TinyMCE V6 WYSIWFY field to the form. Edit Contentlet: Add TinyMCE V6 WYSIWFY field to the form Mar 12, 2024
@rjvelazco rjvelazco self-assigned this Mar 12, 2024
@rjvelazco rjvelazco reopened this Mar 14, 2024
@fmontes
Copy link
Member

fmontes commented Mar 19, 2024

Image

@jcastro-dotcms jcastro-dotcms self-assigned this Mar 20, 2024
@rjvelazco
Copy link
Contributor Author

QA Note:

Remember that this field belongs to the new edit content. In order to see the new field you need to:

  1. Enable the following feature flags:
"DOT_CONTENT_EDITOR2_CONTENT_TYPE":"*"
"DOT_CONTENT_EDITOR2_ENABLED": true
  1. Enable the new edit content for the contentType:

image

@jcastro-dotcms
Copy link
Contributor

INTERNAL QA: PASSED

  • Docker Image: master_latest_SNAPSHOT

The WYSIWYG field is showing up correctly in the new Edit Mode. Just make sure that the new UI in the WYSIWYG looks as specified by Freddy in his comment above.

IMPORTANT: Some options from the previous UI, such as the strikethrough, underscore, adding links, anchors, etc. will be included in the new version in the future. They're out of scope for now.

@josemejias11
Copy link
Contributor

Approved: Tested on dotcms-qa-master.dotcms, Docker, macOS 13.0, FF v121.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment