Release 2.0.1 (#1615)

fix:Update version information and fix typo in system module config

README.md

@@ -15,7 +15,7 @@
 
 
 
-# ImpressCMS 2.0
+# ImpressCMS 2.0.1
 ImpressCMS is a community developed Content Management System build on PHP and MySQL.
 
 This tool makes maintaining a website as easy as writing a word document.

docs/changelog.md

@@ -1,11 +1,21 @@
 # ImpressCMS ChangeLog
 
+## ImpressCMS 2.0.1 
+* Date : 08 Jan 2025
+* DB Version: 48
+* Build Version : 113
+
+Yes, a quick update to fix an embarassing typo that broke the system module. 
+### What's Changed
+#### Bugfixes
+* Fix typo by @fiammybe in https://github.com/ImpressCMS/impresscms/issues/1614
+
 ## ImpressCMS 2.0.0 
 * Date : 06 Jan 2025
 * DB Version: 48
 * Build Version : 112
 
-The first 2.0.0 beta release after the renumbering of the different branches. This version should be feature-complete, but thorough verifications need to be done for the upgrade process and the compatibility with different modules.
+ImpressCMS 2.0.0 final. This release rises the minimal PHP version to PHP 7.4, and supports up to PHP 8.4 included.
 ### What's Changed
 #### Bugfixes
 * Fix mailuser by @fiammybe in https://github.com/ImpressCMS/impresscms/pull/1288

htdocs/include/version.php

@@ -8,7 +8,7 @@
  * @since Xoops
  * @author phppp
  */
-define('ICMS_VERSION_NAME', 'ImpressCMS 2.0.0');
+define('ICMS_VERSION_NAME', 'ImpressCMS 2.0.1');
 
 // For backward compatibility with XOOPS
 define('XOOPS_VERSION', ICMS_VERSION_NAME);
@@ -28,9 +28,9 @@
  *
  * Every release has its own build number, incrementable by 1 everytime we make a release
  */
-// 1.5.0 RC = 107; new 2.0.0 Beta 3=110, new 2.0.0 RC = 111
+// 1.5.0 RC = 107; new 2.0.0 Beta 3=110, new 2.0.0 RC = 111, new 2.0.0 final = 112
 
-define('ICMS_VERSION_BUILD', 112);
+define('ICMS_VERSION_BUILD', 113);
 
 /**
  * Latest dbversion of the System Module

htdocs/modules/system/icms_version.php

@@ -46,7 +46,7 @@
  */
 $modversion = array(
 	'name' => _MI_SYSTEM_NAME,
-	'version' => '2.0.0',
+	'version' => '2.0.1',
 	'description' => _MI_SYSTEM_DESC,
 	'author' => "fiammybe",
 	'credits' => "The ImpressCMS Project",
@@ -64,10 +64,10 @@
 	'image' => "images/system_slogo.png", /* for backward compatibility */
 
 /**  Development information */
-	'status_version' => "2.0.0 Final",
+	'status_version' => "2.0.1 Final",
 	'status' => "Final",
-	'date' => "06 Jan 2025",
-	'author_word' => "",
+	'date' => "08 Jan 2025",
+	'author_word' => "Fixing a typo in the system module",
 	'warning' => _CO_ICMS_WARNING_FINAL,
 
 	/**

release_notes.md

@@ -1,4 +1,4 @@
-# ImpressCMS 2.0.0
+# ImpressCMS 2.0.1
 
 This release of ImpressCMS realizes the majority of the original scope of the 2.0 release, defined almost 10 years ago. The focus is on providing compatibility with newer version of PHP (PHP7.4 up until PHP 8.4) and code cleanup. Existing modules that are compatible with the newer PHP versions should still work, as long as they are not using any of the deprecated functions that have been removed in this release.  
 
@@ -9,7 +9,9 @@ This version, ImpressCMS 2.0.0, does require PHP versions 7.4 and above, and con
 Unzip the contents of the 'htdocs' folder in the root folder of your site, and go in a browser to the address of your site. ImpressCMS will detect that no configuration is present, and will start the installation procedure to help you setup your site on your webserver.
 
 ## Update
-ImpressCMS 2.0 only has overlapping PHP version support with ImpressCMS 1.4.6. When updating from a previous version in the 1.4 or even 1.3 series, first do an upgrade to ImpressCMS 1.4.6 before continuing. When upgrading your PHP, please verify that the modules you use are compatible!
+ImpressCMS 2.0 only has overlapping PHP version support with ImpressCMS starting 1.4.2. When updating from a previous version in the 1.4 or even 1.3 series, first do an upgrade to at least ImpressCMS 1.4.2 before continuing. When upgrading your PHP, please verify that the modules you use are compatible!
+
+Depending on the version you are upgrading from, you can safely remove the /kernel and /class folders after a successful upgrade, those are no longer needed.
 
 ## Known issues