34029 redirect url vtl #34125
Closed
34029 redirect url vtl #34125
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dit mode support - Updated the title custom field template to support a new edit mode using the `DotCustomFieldApi`. - Implemented event listeners for the title box to automatically update the URL and friendly name fields based on the title input. - Improved code structure by separating logic for new edit mode and legacy Dojo implementation. - Ensured backward compatibility by maintaining the original script for non-edit mode scenarios. This change enhances user experience by providing real-time updates and a more modern approach to handling custom fields.
…template integration
…nd template updates
…:dotCMS/core into 34029-task-migrate-pages-vtls-to-new-api
…:dotCMS/core into 34029-task-migrate-pages-vtls-to-new-api
… from native field component
…roved dialog functionality and styling
|
Meticulous was unable to execute a test run for this PR because the most recent commit is associated with multiple PRs. To execute a test run, please try pushing up a new commit that is only associated with this PR. Last updated for commit 13bb7af. This comment will update as new commits are pushed. |
10 tasks
|
|
…ment, enhance data access with new utility methods
…vice for improved data access
…e and DotTruncatePathPipe to improve modularity
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
This pull request introduces a new mechanism for rendering custom fields and previews in the dotCMS UI, enabling support for both the new and legacy edit modes. It modularizes the code by splitting custom field logic and preview code into separate files for new and old modes, and introduces a new SCSS file for consistent field styling in the Angular app. The changes also improve maintainability and future extensibility by isolating mode-specific logic.
Support for new and legacy edit modes:
cachettl_custom_field.vtl,og_preview.vtl,template_custom_field.vtl) to conditionally include either new or old implementations based on whether the new edit mode is enabled. This allows seamless toggling between modern and legacy UI logic. [1] [2] [3]cachettl_custom_field_new.vtl,og_preview_new.vtl) and old edit mode (cachettl_custom_field_old.vtl,og_preview_old.vtl), separating modern JavaScript/HTML from legacy Dojo-based implementations. [1] [2] [3] [4]UI/UX and styling improvements:
native-field.component.scss) for consistent, modern styling of native form fields (inputs, selects, textareas, and buttons) in the Angular app, and registered it in the component. [1] [2]These changes improve code organization, maintainability, and the user experience for both new and legacy edit modes.
Checklist
Additional Info
** any additional useful context or info **
Screenshots
This PR fixes: #34029