Fix: Handle Undefined Window in getOrigin to Prevent SSR Errors

[tmdeveloper007]

Summary of What Has Been Done

Refactored getOrigin to use an explicit guard for browser context. The window.location.origin access is now isolated with explicit typeof window !== 'undefined' and window != null checks.

Changes Made

• utils/urls.ts: Refactored getOrigin with explicit browser context guard

Impact it Made

• Prevents SSR errors during server-side rendering in Next.js
• Makes the function safer across deployment environments

Closes #8846

Note: Please assign this PR to the tmdeveloper007 account.

[retenta-bot]

This pull request addresses the issue of SSR errors by ensuring that the getOrigin function only accesses window.location.origin when the window object is defined. This aligns with previous decisions made to enhance the safety of the function across different deployment environments. Thank you for your contribution!

[Aamod007]

Great fix for SSR compatibility! Creating a dedicated \�rowserOrigin\ variable with strict checks (\ ypeof window !== 'undefined' && window != null) in \utils/urls.ts\ makes the \getOrigin\ function much safer for server-side environments like Next.js. The logic is clean and easy to follow. Approved!