Some findings on migration procedure to 3.2.0.x

[reginfo]

Hi,

Thank you for your hard work on this project.
I attempted the update procedure to version 3.2.0.3 from 3.1.7.5 and noticed a few inconsistencies:

• The steps in the manual differ from those in the migrate_3.2.x.php script.
  For example, according to the manual, after running php migrate_3.2.x.php (Step 3), the next step is to run the web-based upgrade wizard (Step 4). However, this step fails unless the Apache/Nginx configuration is updated beforehand.

• After running php migrate_3.2.x.php (Step 3), the cron job path needs to be updated.
  However, during the web upgrade process (https://<your_teampass_instance>/install/upgrade.php), there is a message stating: "If you had manually defined a job in crontab, you should remove it now."
  Could you please clarify the correct approach here?
  Should the cron job be updated manually, removed entirely, or is it expected that the upgrade process will handle it automatically? In my case, the crontab entry was neither added nor modified automatically.

• On the System Health page, there is an upload limits warning:

PHP allows uploads up to 10M (upload_max_filesize) / 10M (post_max_size). Make sure the front web server allows at least the same: nginx "client_max_body_size", Apache "LimitRequestBody". A lower web-server limit returns HTTP 413 before PHP sees the request.

I’m not sure how to resolve this issue so that the status becomes Operational. Could you please advise on the correct way to fix it?

I have identified an issue and will proceed with opening a support case.