update [Solved] Update from 3.0.213 to 3.0.217 should i remove TinyMCE Standalone module?

[EyeDentify]

Hello PW Gurus.

It´s been a while since i posted here.

I am in the process of deciding to update to 3.0.217 from 3.0.213 and have a question.

I was using the latests standalone version of the TinyMCE module (6.1.5) with my PW 3.0.213 install.

And now the TinyMCE module is in the core with PW 3.0.217 dev as i understand.

Should i remove the standalone TinyMCE module before upgrading to 3.0.217 dev or after ? or at all?

Does it make any difference ?

Hope it make sense, otherwise ask me for more info.

Thanks in advanced.

[monollonom]

Normally copies of core modules inside the site modules’ folder take precedence, so in your case the core TinyMCE module should just be ignored.

[EyeDentify]

  On 5/11/2023 at 1:21 PM, monollonom said:

Normally copies of core modules inside the site modules’ folder take precedence, so in your case the core TinyMCE module should just be ignored.

Expand  

Thank You Sir for your answer.

Then i can safle go ahead and update.

/EyeDentify

[monollonom]

Small FYI: apparently I was wrong... I updated my local setup to 3.0.217 and after refreshing the modules I got a notification inviting me to choose which copy of the duplicate module to use:

This was after I confirmed but by default it seemed to have the core one selected.

Though there are no problems to report because of this

[EyeDentify]

  On 5/15/2023 at 1:19 PM, monollonom said:

Small FYI: apparently I was wrong... I updated my local setup to 3.0.217 and after refreshing the modules I got a notification inviting me to choose which copy of the duplicate module to use:

This was after I confirmed but by default it seemed to have the core one selected.

Though there are no problems to report because of this

Expand  

Hello Again Processwire Gurus.

Yes i discovered when upgrading that Processwire asked me wich module i wanted to use and had the core module pre-selected as default.
I just had to delete the standalone one and do a refresh under modules and everything worked like a charm.