SOLVED How do I create a post in Group?

[Esha]

@dunlix yes we are yet to plan the upgrade. Can you share with me a list of new features we can see in the latest release? I will need to do a code review with my team to run impact analysis on upgrading to the latest version.

I have reviewed the release notes, but they are too technical for me to understand

[PitaJ]

@esha you should really upgrade more often as you're missing out on several security fixes.

You can check the blog for more high level overviews for each release:

NodeBB Development Blog

[dunlix]

@esha The feature list would be endless, as you are running several years behind. One of those features is what i showed, I don't even know how long ago it was added.
https://github.com/NodeBB/NodeBB/releases
youd have too look at ALL changes SINCE v1.11.2. Very long ago

[Esha]

@pitaj thanks a ton. This is exactly what I have been looking for past months

[Esha]

@dunlix yes we are yet to plan the upgrade. Issue is, we have made a lot of customizations in core NodeBB to match our requirements. We are working on impact analysis to see what code breaks and fixes we can encounter with the latest upgrade.

[dunlix]

@esha you could backup your database, your NodeBB uploads folder (as seen in docs) and the entire NodeBB root folder. Then upgrade as usual, and if anything breaks, then simply restore everything from the backup.

What did you change in core?

[arc002]

@dunlix i really appreciate your support. Below are few files in which we have made changes
TPL files
Login
Register
topic_list
topic

JS files
nodebb-plugin-category-notifications(js)
index.js(src/topics)
index.js(src/routes)
and many more like these core files.

[Esha]

@arc002 thanks for listing out the details here.

@dunlix mentioned here are few of the changes that we have done. There's a huge list.

[dunlix]

@esha @arc002 huh. I suppose you can just move the modified files to the new installation, and if too buggy or just too complicated, you can revert to your backup.

[PitaJ]

The easiest way is to use git to apply the same changes to the new files.

You can create a patch and then apply that patch to an upgraded clone of the repository. Git will tell you when conflicts occur and you can fix those manually.

Do note this is exactly why we recommend using a plugin for customization: it's much easier to keep plugins up to date than modify your customizations to core every time we modify the file.