Upgrade to v8.2.0 has legacy .htaccess bug

[sstahn]

Issue

After upgrading from the previous v8.1.3 to v8.2.0 as per the 'upgrade' section of the docs, I received an "internal server error". Investigation revealed that the line in the /public/legacy/.htaccess file was

RewriteBase suitecrm.fqdn.comlegacy/

It was exactly as above, no slash after the FQDN (which has been changed from mine).

I changed it to
RewriteBase /public

And now the system works as expected. (Or at least lets me log in and start testing for other issues.)

Expected Behavior

It probably should not have the FQDN in the RewriteBase line... but I'm not an Apache expert.

Actual Behavior

As per issue statement:
the line in the /public/legacy/.htaccess file was

RewriteBase suitecrm.fqdn.comlegacy/

It was exactly as above, no slash after the FQDN (which has been changed from mine).

Possible Fix

I changed it to
RewriteBase /public

Steps to Reproduce

Not sure of exact steps but suspect prerequisite factors are:
v8.1.3
have a working FQDN system
upgrade to v8.2.0 using the steps listed in the docs. (I followed them exactly, as it's the first upgrade I've done.)

Context

Stuff failed to run.

Your Environment

• SuiteCRM Version used:
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)):
• Environment name and version (e.g. MySQL, PHP 7):
• Operating System and version (e.g Ubuntu 16.04):

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

Apache2
MariaDB

All patched with release patches (using aptitude) as of this morning, prior to the SuiteCRM upgrade attempt.