Update 5.3 - Revision history

Regify: /* 2) Save a footer image */

2026-03-16T07:24:46Z

2) Save a footer image

2023-05-09T06:39:15Z

5) Disable maintenance mode

2023-04-24T09:27:18Z

Starting the upgrade

2023-04-20T11:01:00Z

Branding and Corporate Identity

2023-04-20T10:20:46Z

Finish with a restart

2023-04-20T10:19:32Z

Finish with restart

2023-04-20T10:18:46Z

1) Note shop prices

2023-04-20T10:14:29Z

Generic information

2023-04-20T10:13:29Z

Generic information

2023-04-20T10:12:18Z

Generic information

@@ Line 24: / Line 24: @@
 === 2) Save a footer image ===
-The update will delete your manually changed footer code as it will no longer work. It replaces it by some default footer with the most used options and links. You can later modify the footer again but a screenshot of the previous footer is very helpful for that.
+Make a screenshot of the current footer. The update will delete your manually changed footer code as it will no longer work like this. The update replaces it by some default footer with the most used options and links. You can later modify the footer again and a screenshot of the previous footer is very helpful for that.
 === 3) Enable maintenance mode ===

@@ Line 50: / Line 50: @@
 === 5) Disable maintenance mode ===
-Now, please re-login to your web-administration and go to "Provider maintenance". Disable maintenance mode by clicking "Remove maintenance mode" on the upper left.
+Now, upon the update is finished and the system was restarted, please re-login to your web-administration and go to "Provider maintenance". Disable maintenance mode by clicking "Remove maintenance mode" on the upper left.
 == Finish with a restart==

@@ Line 22: / Line 22: @@
 Please note the '''Value''' then from "shop_standard.json" and "shop_group.json" for both 1 and 2 years. This should represent the price including VAT.
-=== 2) Enable maintenance mode ===
+=== 2) Save a footer image ===
 Please log-in to your web-administration and go to "Provider maintenance". Enable maintenance mode by clicking "Enable maintenance mode" on the upper left.
-=== 3) Do the update ===
+=== 4) Do the update ===
 To update your regify provider appliance, please log in via SSH (or PuTTY).
@@ Line 44: / Line 48: @@
 If you are running a redundant system in master-slave-replication, '''start with the master system'''. Upgrade the slave directly after the master appliance.
-=== 4) Disable maintenance mode ===
+=== 5) Disable maintenance mode ===
 Now, please re-login to your web-administration and go to "Provider maintenance". Disable maintenance mode by clicking "Remove maintenance mode" on the upper left.

@@ Line 87: / Line 87: @@
 We identified the '''color''' as the main customization target for most regify providers. Therefore, you can now easily set your corporate color and let the system style the elements for you. Enter your (sub)provider web-administration and go to "Provider settings". In the "Contact" panel you can select the color and save. If you are the main provider administrator, you can do that for your subproviders, too. In web administration "Manage sub-providers". The "Common" tab offers the base colour selection, too.
-Please note that you very likely need to refresh your webbrowser page using Ctrl+F5 to see the new generated CSS (otherwise your webbrowser uses a cached version).
+Please note that you very likely need to refresh your webbrowser page using Ctrl+F5 to see the new generated CSS (otherwise your webbrowser uses a cached version). End users webbrowsers will load the new CSS latest on the next day.
 === Customized codeFooter.php ===

@@ Line 49: / Line 49: @@
 == Finish with a restart==
-The update also updates the kernel of the system, so you need to make a restart after the update has finished. The upate will ask you for a restart and you should answer with YES.
+The update also updates the kernel of the system, so you need to make a restart after the update has finished.
 '''NOTE:''' Logged in using SSH (PuTTY), you can restart the appliance using the appliance menu "Appliance..." -> "Other Settings..." -> "Reboot the appliance".
-In case you log in with root account, you can also enter
+'''NOTE:''' In case you log in with root account, you can also enter
   shutdown -r now
-'''NOTE:''' The shutdown can take a minute or even more. Please do not power off the machine during restart manually.
+'''NOTE:''' The shutdown can take a minute or even more. Do not power off the machine during restart!
 == ToDo after upgrading ==

@@ Line 7: / Line 7: @@
 === 1) Note shop prices ===
-The shop system has changed and you have to verify the prices for regimail ''Professional'' in the updated system. We try to get the prices and VAT from your old shop configuration after the update, but it may fail. So you need to know the prices!
+The shop system has changed and you have to verify the prices for regimail ''Professional'' in the updated system. The appliance tries to migrate the prices and VAT from your old shop configuration, but it may fail. So you need to know the prices!
-Please log-in to your web-administration and go to "Provider settings". Open the files "shop_standard.json" and "shop_group.json", scroll close to the bottom and note the "Price" and "Value" fields you find for 1 and 2 years. They look similar to this example (2 years):
+Best to log-in to your web-administration and go to "Provider settings". Open the files "shop_standard.json" and "shop_group.json", scroll close to the bottom and note the "Price" and "Value" fields you find for 1 and 2 years. They look similar to this example (here the 2 years section):
+   {
@@ Line 20: / Line 20: @@
+   }
-Please note the '''prices including VAT''' from "shop_standard.json" and "shop_group.json" for both 1 and 2 years.
+Please note the '''Value''' then from "shop_standard.json" and "shop_group.json" for both 1 and 2 years. This should represent the price including VAT.
 === 2) Enable maintenance mode ===

@@ Line 1: / Line 1: @@
 == Generic information ==
-The whole update with restart usually takes less than 7 minutes. During that time, the users are not able to use the system!
+<div style="font-size: 140%; font-weight: bold; background-color: #ffeeee; border: 2px solid red; padding: 6px;">The update including restart can take 10 to 15 minutes <u>or even more</u>, depending on the amount of data in your system, the network connection speed and the system i/o speed. We suggest to plan for that. During that time, the users are not able to use the system!</div>
 == Starting the upgrade ==

@@ Line 3: / Line 3: @@
 The whole update with restart usually takes less than 7 minutes. During that time, the users are not able to use the system!
-<span style="font-size: 140%; font-weight: bold;">But it can take 10 to 15 minutes <u>or even more</u>, depending on the amount of data in your system, the network connection speed and the system i/o speed. We suggest to plan for that.</span>
+<div style="font-size: 140%; font-weight: bold; background-color: #ffeeee; border: 2px solid red; padding: 6px;">But it can take 10 to 15 minutes <u>or even more</u>, depending on the amount of data in your system, the network connection speed and the system i/o speed. We suggest to plan for that.</div>
 == Starting the upgrade ==