Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Block Locking in Tour Operator Block Templates, Patterns, and Blocks #405

Open
8 tasks
ashleyshaw opened this issue Oct 10, 2024 · 0 comments
Open
8 tasks
Assignees
Labels
[Component] Block Locking [Type] Discussion For issues that are high-level and not yet ready to implement.

Comments

@ashleyshaw
Copy link
Member

Description

We need to plan out the implementation of block locking for the Tour Operator Plugin to control user editing capabilities effectively. This will ensure content consistency and maintain design integrity across all block templates, patterns, and blocks.

Objectives

  • Identify which blocks should have editing restrictions.
  • Determine where template and block locking should be applied (patterns, templates, individual blocks).
  • Define the level of locking (e.g., prevent moving, removing, or modifying blocks).

Tasks

  • Review all existing block templates and patterns to decide where block locking is required.
  • Identify key blocks in the Tour Operator plugin that need partial or full locking.
  • Implement template locking to restrict changes to predefined templates.
  • Use block locking to limit modifications on critical components (e.g., navigation blocks, headers).
  • Test the locked blocks to ensure that they behave as expected and maintain their structure.

Acceptance Criteria

  • The locked blocks and templates must prevent unintended user modifications.
  • Block locking should not hinder necessary customization by admins or advanced users.
  • The implementation should be compatible with the WordPress block editor.

Additional Resources

@ashleyshaw ashleyshaw added [Type] Discussion For issues that are high-level and not yet ready to implement. [Component] Block Locking labels Oct 10, 2024
@github-project-automation github-project-automation bot moved this to Needs Triage in Tour Operator Oct 10, 2024
@ZaredRogers ZaredRogers added this to the 2.0.0 milestone Oct 11, 2024
@ZaredRogers ZaredRogers self-assigned this Oct 11, 2024
@ZaredRogers ZaredRogers moved this from Needs Triage to 🗣️ In Discussion in Tour Operator Oct 11, 2024
@ashleyshaw ashleyshaw removed this from the 2.0.0 milestone Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Component] Block Locking [Type] Discussion For issues that are high-level and not yet ready to implement.
Projects
Status: Needs Design
Development

No branches or pull requests

2 participants