Redirect to custom path per node

Found missing declarations, so added the patch again

I've tested the feature on my side by using the patch from comment #4 ✨ Redirect to custom path per node Needs review and it's working perfectly.

For me that new feature could be added in the new release. It's really useful to have an option to add a custom path redirect per node.

Updating patch as the base field plugin type was set to textfield instead of string_textfield. This was causing errors on config import and field creation

Thanks for the update xiwar →

Identified issues in previous patch:

1. The Unpublished Redirect Destination field is incorrectly displayed for all content types, even when disabled in settings.
2. The field accepts URLs without a leading slash (/), causing redirect execution errors
3. Error: Call to a member function isEnabledCustomPath() on null

Attached updated patch with fixes (see interdiff file for changes).

@ressinel patch is Working Fine as per the issue scope but in that if we add the Internal redirect path as node/60 the it throw the error if we access the unpublished node

The website encountered an unexpected error. Try again later.
InvalidArgumentException: The internal path component 'node/60' is invalid. Its path component must have a leading slash, e.g. internal:/foo. in Drupal\Core\Url::fromInternalUri() (line 416 of core/lib/Drupal/Core/Url.php).

I think we should add validation on the Internal Redirect Path field during configuration save. It should ensure that the path starts with a "/" and show a validation error if it doesn't.

Thanks!

Or either we can add the description like this .
The path has to start with a slash.