[wp-trac] [WordPress Trac] #31596: Make it easier to update TinyMCE

[WordPress Trac]

#31596: Make it easier to update TinyMCE
----------------------------+-----------------------------
 Reporter:  iseulde         |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  low             |   Milestone:  Future Release
Component:  TinyMCE         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  javascript
----------------------------+-----------------------------
Changes (by azaozz):

 * keywords:  needs-patch needs-docs =>
 * type:  defect (bug) => task (blessed)


Comment:

 Updating TinyMCE is quite straightforward now. It is as simple as copying
 over the new files from the `dev` package to
 `/src/js/_enqueues/vendor/tinymce/`. This should include the `/themes`,
 `/skins`, and the subset of default `/plugins` WP is using. All of the
 default (upstream) TinyMCE tests have been removed as they don't make
 sense to run in WP any more.

 There were few "hacks" before but all have been removed for quite some
 time. The only remaining inconsistency in the WP implementation is that
 after copying the new files the `tiny_mce_popup.js` file and `utils`
 directory have to be moved to the root `/tinymce` directory from
 `/plugins/compat3x/`, and changes to `/plugins/compat3x/css/dialog.css`
 have to be reverted. Both of these are needed to support super old custom
 TinyMCE plugins from version 3.x (5+ years).

 The only other change is to update `$tinymce_version` in `wp-
 includes/version.php` with the new version string. This is used mostly to
 break caches and (historically) contains the date the update was made in a
 `yyyymmdd` format.

 This applies to updating TinyMCE's 4.9.x branch. Changing to "task" and
 leaving open so it's easier to find in case it's needed :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/31596#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform