Fixes #3919 & improve routing

[mohit-nagaraj]

Pull Request Description

This PR implements one bug fix (#3919) and one enhancement:

Bug Fix:

• Issue: Resolved the navigation issue when accessing specific routes.
• Resolution: Ensured smooth navigation by addressing the underlying cause of the routing problem.

Feature Improvement:

• Enhancement: Improved the "Close Meeting" functionality.
• Details: Removed the reliance on direct HTML links, streamlining the process and making it more user-friendly.

Please review the changes and let me know if you have any questions or feedback!

[jitsi-jenkins]

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

[damencho]

This change will break the redirection to close3.html for everyone.

[mohit-nagaraj]

Hey Yea yea, i too noticed it being used in another place and plan to fix it there as well. Thanks again for pointing it out

…

On Sun, Jan 5, 2025, 5:46 AM Дамян Минков ***@***.***> wrote: This change will break the redirection to close3.html for everyone. — Reply to this email directly, view it on GitHub <#15446 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZHAGG6XVRLR4Y2M4ZD4GK32JB2WRAVCNFSM6AAAAABUTIGV2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGQ2DQOBQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[damencho]

No, you cannot change the path and require backend changes(webserver configuration), as those that have installed it via Debian packages will not have that change and that will stop working for them.

[damencho]

Just do not change the path of the files.

[mohit-nagaraj]

hey,
I have a few things to ask you out

as those that have installed it via Debian packages will not have that change and that will stop working for them

the close3.html will still be acessible right cuz all the files in static are served as it and we arent restricting any of them, i have used another route which aliases to tht file

Just do not change the path of the files.

change path of the file like as in changing the actual path of the file? idts i am modifying it anywhere

[damencho]

the close3.html will still be acessible right cuz all the files in static are served as it and we arent restricting any of them

No, it is no longer accessible after your change, as it is behind a path /close and none of the existing deployments will match this path to close3.html file.