Step 1: Stop all relevant services and the OFORK daemon

Make sure that no running services or cron jobs are still trying to access OFORK.
This depends on your service configuration. Example:

root> /etc/init.d/cron stop
root> /etc/init.d/postfix stop
root> /etc/init.d/apache stop

Stop OFORK cron jobs and the daemon in this order:

ofork> cd /opt/ofork/
ofork> bin/Cron.sh stop
ofork> bin/ofork.Daemon.pl stop

Step 2: Back up the database and the existing OFORK installation

shell> cd /opt
shell> mv ofork ofork-old

Step 3: Install OFORK using ofork-12.0.1.tar.gz

First download the source archive as a .tar.gz file – OFORK 12 Patch Level 1 tar.gz.
Extract the archive into /opt and rename the directory from ofork-12.0.1 to ofork.

shell> cd /opt
shell> wget https://ftp.o-fork.de/ofork-12.0.1.tar.gz
shell> tar xzf ofork-12.0.1.tar.gz
shell> mv ofork-12.0.1 ofork

Step 4: Adjust Config.pm

Copy the file /opt/ofork-old/Kernel/Config.pm to /opt/ofork/Kernel/Config.pm.

Note: If you did not install OFORK in the default path /opt/ofork/..., you must adjust the paths in /opt/ofork/Kernel/Config.pm.

Step 5: Restore article data

If your OFORK system stores article data in the file system, you need to restore the article directory from /opt/ofork-old/var/
or from the directory configured in your system settings.
Copy the corresponding directory into the new OFORK installation.

Step 6: File permissions

Run the following command as the root user to set the correct file and directory permissions for OFORK.
The script will try to detect the proper user and group settings for your setup.

shell> cd /opt/ofork/
shell> bin/ofork.SetPermissions.pl

Note: In some cases, the following Perl modules may also need to be installed:
cpan install Moo
cpan install Types::Standard
or
sudo apt-get install -y libtypes-path-tiny-perl
sudo apt-get install -y libmoo-perl

Step 7: Run the migration script

Note: The migration script may ask you to set a time zone for OFORK.
It is very important to keep the correct time zone setting (OFORKTimeZone) for data storage.
Otherwise, the date and time of data added after the update (tickets, articles, etc.) may be stored using a different time zone.

Run the migration script as user ofork, not as root:

ofork> cd /opt/ofork/
ofork> scripts/DBUpdate-to-12.pl

Step 8: Restart your services

This depends on your service configuration. Example:

root> /etc/init.d/apache start
root> /etc/init.d/postfix start
root> /etc/init.d/cron start

Note: If you get a 500 error when opening OFORK in the browser, please delete the file ZZZAAuto.pm.
After that, OFORK should load normally again.

shell> cd /opt/ofork/Kernel/Config/Files
shell> rm ZZZAAuto.pm

Step 9: Start the OFORK daemon

The OFORK daemon is responsible for asynchronous and recurring tasks in OFORK.
It also handles all GenericAgent jobs and must be started by the ofork user.

shell> /opt/ofork/bin/ofork.Daemon.pl start

Note: If you have problems with the update, you can send a message to support@o-fork.com.
Our professional services will be happy to help.