All about changelog.txt?

researchcooperative
@researchcooperative
6 years ago
694 posts
Today I was advised: "Any time changes are made to a skin, the templates modified will be in the changelog.txt file"

I will look for this, as instructed, but in order to understand the advice, I went to the support forums, glossary and JR documentation and did not find any explicit discussion of changelog.txt files.

The name changelog.txt is self-explanatory as far as purpose is concerned, but does not tell me where the change log is located.

I expect it is easy to find, if one already knows where it is.

Probably I will find it if I scroll around in the skin template files area of my ACP.

Still, it would be nice if I could go directly to a basic explanation of where the changelog.txt is, and whether there is just one or many of them, and how they are used in JR... e.g. in the JR glossary (in the JR documentation).

Knowing how systematically JR has been built, there are probably changelog.txt files automatically created for every area of activity, front and back of the system.

It would be nice to know more about them, if this is the case.

Thanks.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

updated by @researchcooperative: 04/11/18 06:19:35AM
brian
@brian
6 years ago
10,148 posts
There's several ways to see this:

1) Click on the "Help" tab for any module or skin. You will see one of the options is "View information about this item including detailed Change Log"

2) You can view the changelog directly here on Jamroom.net - i.e.:

https://www.jamroom.net/the-jamroom-network/networkmarket/107/smiley-support

click on "View Changelog"

3) When you are in the Marketplace module doing an UPDATE you can click on the "Changes" button to see the changes before updating.

Hopefully it is linked to in enough obvious places that we don't need to add it anywhere else, but let me know.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
researchcooperative
@researchcooperative
6 years ago
694 posts
brian:
1) Click on the "Help" tab for any module or skin. You will see one of the options is "View information about this item including detailed Change Log"

When looking for this through my ACP, I found that the full route for a module is:

Module>Help>Product Detail>View Changelog
....
The changelog tells us when and why changes were made, and identifies the Version number, which can be referred to when looking at template versions with the compare tool.
....
brian:
Hopefully it is linked to in enough obvious places that we don't need to add it anywhere else, but let me know.

When I tried the same route for the skin modules (jrNingja and jrSlate_SiteBuilder) I reached the Help level, but was shown a red button with the message "Item not found - please try again"

So it seems this is not the way to find a Change Log for a skin module. Where to go?


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
michael
@michael
6 years ago
7,714 posts
All the changelogs can be found via:
ACP -> MODULES -> CORE -> MARKETPLACE -> reload modules or skins

You'll see 'changelog' link that will open a popup window.
changelog.jpg
changelog.jpg  •  152KB

researchcooperative
@researchcooperative
6 years ago
694 posts
Thanks,

The full route I found is:

ACP -> MODULES -> CORE -> MARKETPLACE -> TOOLS -> RELOAD MODULES OR SKINS -> CHANGES

It's all there!

Now I am wondering what exactly "Reload" means (one of the Tools found on the above route).

Is this what we should use if we need to Reinstall a possibly corrupted module or skin? The label seems self-explanatory, but maybe there is more to it than this.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
michael
@michael
6 years ago
7,714 posts
Reload means to re-download the copy from jamroom.net.

Example:
You have version 1.5.0 of some module, I fix it and upload version 1.5.1. You say "it still has a problem", so I upload ANOTHER change.

In this circumstance, the thing being fixed is still in version 1.5.1, so rather than changing the version to 1.5.2 i'll as you to "reload" the module.