403 Forbidden error after server migration
Installation and Configuration
Under those circumstances I would copy the /modules directory from the working jamroom install over to the non-working install and see what happens.
Rename (or backup/delete) the current /modules.
Seems like a good first step.
Would also copy the hidden /.htaccess from the working version too.
--edit--
Another possibility is: symlinks
The base location for a module is on a directory without its version number.
eg:
/modules/jrCore
When a new jrCore is updated from the marketplace, the current jrCore will move to a version number
/modules/jrCore-version-1.2.3
/modules/jrCore-version-1.2.4
/modules/jrCore-version-1.2.5
But the base
/modules/jrCore
will point to the highest version number via a symlink on /modules/jrCore
Its totally valid to keep just the most recent version of any of the modules and remove its version number, then delete the others, so if you had
/modules/jrCore-version-1.2.3
/modules/jrCore-version-1.2.4
/modules/jrCore-version-1.2.5
you could rename
/modules/jrCore-version-1.2.5
to
/modules/jrCore
and delete:
/modules/jrCore-version-1.2.3
/modules/jrCore-version-1.2.4
Then when the marketplace did its update it would re-add a new symlink
updated by @michael: 07/29/19 08:50:27PM