VE-6750

[csAdityaPachauri]

Summary

This PR fixes a bug where the "Start Editing" button would cause an "entry not found" error in the Visual Builder if the page's URL contained query parameters or a hash. The target-url is now generated using only the base path of the URL, ensuring the correct entry is always found.

Fix

The getVisualBuilderRedirectionUrl function was updated to construct the target-url using window.location.origin + window.location.pathname. This effectively strips any query parameters and hash fragments, providing a clean URL that the backend can correctly resolve.

Uploading Screen Recording 2025-07-18 at 4.41.05 PM.mov…

[hiteshshetty-dev]

Please add test cases and make pr on develop_v3 branch

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	71.83%	9051 / 12600
🔵	Statements	71.83%	9051 / 12600
🔵	Functions	71.68%	324 / 452
🔵	Branches	84.3%	1139 / 1351

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
src/visualBuilder/utils/getVisualBuilderRedirectionUrl.ts	100%	100%	100%	100%

Generated in workflow #476 for commit c0f6a83 by the Vitest Coverage Report Action

[faraazb]

Also, hash routing needs to be considered. This won't work with hash router.

[csAyushDubey]

Posted one doubt

[csAyushDubey]

I have one doubt, if we remove search params are we sure the user's website will not have any impact? I mean how are we making sure removing the params would not break/change the user's website.
@faraazb @hiteshshetty-dev @sairajchouhan @csAdityaPachauri

[sairajchouhan]

that's a valid point, not sure removing all the query params is a good decision

[csAdityaPachauri]

@hiteshshetty-dev @faraazb @sairajchouhan As discussed, it would be better to make changes on the VB side for this. So closing this PR