What happens with modified files when JReviews is upgraded

From JReviews Documentation
Revision as of 11:25, 20 August 2010 by Jreviews (Talk | contribs)

Jump to: navigation, search

When JReviews is reinstalled or upgraded, the whole /components/com_jreviews folder is deleted and replaced with new version, that is why it is important to make modifications outside /com_jreviews as instructed in JReviews Code Overrides


Having modified files in overrides folder will keep them safe, but the files you modified might be changed in a new version of JReviews because of bug fixes or new features.


It is important that you update your modified files with changes that come with new JReviews.

You will need to compare each modified file with the same unmodified file in latest JReviews and:

  • update your modified file with changes in new version
  • or copy the new version of the file and re-do your modifications


If a file has a lot of changes in the new version, second option might be better because what you are more familiar with your old modifications and re-do ing them will be easier than implementing our changes into your modified file.


Comparing files for differences would be difficult without some tools. You can use Beyond Compare (commercial) or WinMerge (open source).


Here is an example of listings_blogview.thtml file comparison between JReviews versions 2.1.23.162 and 2.2.02.168 using WinMerge:

FileComparison.png