Laravel octane (not merge)

[rodriquelca]

Issue & Reproduction Steps

When running ProcessMaker with Laravel Octane, the application may reuse service container instances across requests. The SetLocale middleware relied on App::setLocale(), which indirectly depends on application configuration services.

In scenarios where a stale or invalid configuration binding exists within a long-lived Octane worker, locale initialization can fail and affect request processing.

Solution

The SetLocale middleware was updated to make locale initialization more resilient when running under Laravel Octane.

current

with octane

How to Test

1. Log in with a user configured with language en.
2. Verify the application is displayed in English.
3. Change the user's language to another supported locale (for example es).
4. Refresh the application.
5. Verify translations are displayed in the selected language.
6. Verify localized date formatting continues to work correctly.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-31695

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.