What happens with modified files when JReviews is upgraded

From JReviews Documentation
Revision as of 17:08, 30 August 2010 by Alejandro (Talk | contribs)

Jump to: navigation, search

When JReviews is re-installed or upgraded, the whole /components/com_jreviews folder is replaced with new version, which is why it is important to make your modifications outside /com_jreviews as instructed in JReviews Code Overrides

When you upgrade JReviews it is important that you also update any modified files with changes in the newer version. This is to ensure your modified files include bug fixes and new features. You will need to compare each modified file with the same unmodified file in the newer version 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 many changes in the new version, a second option might be better because you are more familiar with your old modifications and re-doing them will be easier than implementing new 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

Retrieved from "https://docs.jreviews.com/index.php?title=What_happens_with_modified_files_when_JReviews_is_upgraded&oldid=1572"