Extra Commands Needed for Upgrade

[PitaJ]

One more thing:

If you do have problems upgrading to 1.7.1 which will release next week, can you message me here, and I can help you remedy those issues permanently.

[scarycanary]

I certainly will thanks a lot

[scarycanary]

Is Slick going to work in 1.7.1 ?

[PitaJ]

@billygrande you should be able to run npm i [email protected] and that version of slick will work with NodeBB 1.7.0

[scarycanary]

Thanks I think I have that version already because I needed it for 1.7.0

[PitaJ]

Oh, yeah, sorry, I thought you said 1.7.0

Yes, if it works with 1.7.0 it should work with 1.7.1

[scarycanary]

Hi
Tried to run the hard git and got this :

ambiguous argument 'origin/1.7.x': unknown revision or path not in the working tree.

[PitaJ]

My bad. I forgot the v. The full command should be git reset --hard origin/v1.7.x

[scarycanary]

Thanks should have spotted that myself

[scarycanary]

@pitaj Thanks for your response regarding plugin (I'm restricted on forum responses and my time is limited)

Do I need to do a merge after this as I got some kind of message after the hard git mentioning that (forgot to copy it). I ran the hard git then an upgrade. Everything is working fine.

[PitaJ]

Hopefully you don't need to do anything for the upcoming v1.7.1 upgrade.

In the meantime, can you do git status and paste the output of that? Maybe it will provide some useful information.

[scarycanary]

# On branch v1.7.x
#
# It took 2.10 seconds to enumerate untracked files. 'status -uno'
# may speed it up, but you have to be careful not to forget to add
# new files yourself (see 'git help status').
nothing to commit, working directory clean

[PitaJ]

@billygrande ok as far as I can tell, you should be good when upgrading to the next version. Of course, let me know if that's not the case.