NPM Resource Changed ? Pending

User tests: Successful: Unsuccessful:

avatar brianteeman
brianteeman
14 Jan 2020

TinyMce follows semantic versioning. There is no reason that we should be locked down to an old patch release of 5.0.14 when the current is 5.1.5

Some help fixing the javascript in build\build-modules-js\init.es6.js to write the correct version number in the plugin xml would be appreciated

avatar brianteeman brianteeman - open - 14 Jan 2020
avatar brianteeman brianteeman - change - 14 Jan 2020
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 14 Jan 2020
Category NPM Change Front End Plugins
avatar jwaisner jwaisner - test_item - 14 Jan 2020 - Tested successfully
avatar jwaisner
jwaisner - comment - 14 Jan 2020

I have tested this item successfully on b620847

Tested all functions of Tinymce on backend and frontend. Everything works as intended.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/27520.

avatar brianteeman brianteeman - change - 14 Jan 2020
Labels Added: NPM Resource Changed ?
avatar brianteeman
brianteeman - comment - 15 Jan 2020

Thanks. I will test and merge in the morning.

avatar joomla-cms-bot joomla-cms-bot - change - 15 Jan 2020
Category NPM Change Front End Plugins JavaScript Repository NPM Change Front End Plugins
avatar brianteeman
brianteeman - comment - 15 Jan 2020

@SharkyKZ I applied your pr and ran npm i
but the version in the xml is still
<version>^5.1.0</version>
did i miss something?

avatar SharkyKZ
SharkyKZ - comment - 16 Jan 2020

It's because regex for replacing version expects a valid version in XML. As a quick fix you can manually change the version just in the XML to something valid (e.g. back to 5.0.14) and then run npm install again.

avatar SharkyKZ
SharkyKZ - comment - 16 Jan 2020

Although I don't see the need for such specific regex. We could simplify it. See brianteeman#91.

avatar brianteeman brianteeman - change - 17 Jan 2020
The description was changed
avatar brianteeman brianteeman - edited - 17 Jan 2020
avatar brianteeman
brianteeman - comment - 17 Jan 2020

Thanks @SharkyKZ the regex works perfectly now.

avatar jwaisner
jwaisner - comment - 17 Jan 2020

@brianteeman During testing everything works as expected, just need to confirm that the version presented in the extension manager will still be 5.0.14 or should that show 5.1.5?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/27520.

avatar SharkyKZ
SharkyKZ - comment - 17 Jan 2020

It will probably show 5.0.14. You can use Refresh Cache button to update data from manifest.

@brianteeman You still need to commit XML changes to correct version.

avatar jwaisner
jwaisner - comment - 17 Jan 2020

Refreshing the Cache worked. I noticed the version shows as "^5.1.0". Is that supposed to have the "^" in the version number? Changing <version>^5.1.0</version> to <version>5.1.0</version> corrects this. I dont fully understand the versioning in Tinymce, so this may be normal.

avatar jwaisner jwaisner - test_item - 19 Jan 2020 - Tested successfully
avatar jwaisner
jwaisner - comment - 19 Jan 2020

I have tested this item successfully on ed91398


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/27520.

avatar brianteeman
brianteeman - comment - 30 Jan 2020

Can someone please check and merge this as it addresses a security vulnerability

avatar SharkyKZ
SharkyKZ - comment - 30 Jan 2020

You still need to run npm install to update the XML with correct version.

f62c282 30 Jan 2020 avatar brianteeman xml
avatar brianteeman
brianteeman - comment - 30 Jan 2020

@SharkyKZ doh - done now

avatar brianteeman
brianteeman - comment - 5 Feb 2020

Can someone please check and merge this as it addresses a security vulnerability

avatar rdeutz rdeutz - change - 5 Feb 2020
Status Pending Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2020-02-05 17:43:34
Closed_By rdeutz
avatar rdeutz rdeutz - close - 5 Feb 2020
avatar rdeutz rdeutz - merge - 5 Feb 2020
avatar brianteeman
brianteeman - comment - 5 Feb 2020

Thanks

Add a Comment

Login with GitHub to post a comment