Jump to content

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


EyeDentify
 Share

Recommended Posts

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.

  • Like 1
Link to comment
Share on other sites

4 hours ago, 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.

Thank You Sir for your answer.

Then i can safle go ahead and update.

/EyeDentify

Link to comment
Share on other sites

  • EyeDentify changed the title to [Solved] Update from 3.0.213 to 3.0.217 should i remove TinyMCE Standalone module?

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:

2005340577_Screenshot2023-05-15at15_12_45.thumb.png.8a159e85f5990ffb7ea407df7b443566.png

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

1324751024_Screenshot2023-05-15at15_12_55.thumb.png.f4c96fda875738dd49395b56468d9152.png

Though there are no problems to report because of this

  • Like 1
Link to comment
Share on other sites

On 5/15/2023 at 3: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:

2005340577_Screenshot2023-05-15at15_12_45.thumb.png.8a159e85f5990ffb7ea407df7b443566.png

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

1324751024_Screenshot2023-05-15at15_12_55.thumb.png.f4c96fda875738dd49395b56468d9152.png

Though there are no problems to report because of this

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.

 

  • Like 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...