Yesterday, I was trying to update the Payment Method settings from the Configuration section in Bagisto, but I was continuously getting a 403 Forbidden error whenever I tried to save the changes.

At that time, a support member suggested that I update my Bagisto installation from the master branch to the latest 2.4 branch.

I updated my installation to the latest 2.4 version, and the Payment Method error no longer occurs. However, I am still facing the same 403 Forbidden error in other modules under the Configuration section.

It seems that the issue is not limited to the Payment Method configuration and may be related to the configuration save/update functionality or permissions.

Could someone please guide me on:

What could be causing the 403 Forbidden error across the Configuration modules?
Is there any additional migration, permission, cache, or configuration change required after updating from the master branch to 2.4?
Is there any recommended way to properly update/sync the latest 2.4 branch in an existing Bagisto installation?
Are there any specific routes, middleware, CSRF, ACL/permission, or server configuration settings I should check?

Current situation:

Previous version: Master branch
Updated version: Latest 2.4 branch
Payment Method: Working after the update
Other Configuration modules: Still returning 403 Forbidden

Any guidance on how to properly resolve this issue would be greatly appreciated.

Thank you.