Build your WordPress website with Elementor.Discover Elementor Affiliate link
Français

Site appearance

Editor and content · Beginner to intermediate

Locked WordPress block: how to move or delete it

Does a WordPress block refuse to move or disappear? Identify the lock, pattern and template, then change the correct protection without disrupting other pages.

Source published: · Source updated: · Editorial policy

Read the French edition

Recognize what prevents the action

You can read a block and sometimes edit its text, but commands for moving or deleting it are missing. A padlock may appear in its toolbar or List View. The goal is to make the intended change to the correct content while preserving useful protections and other pages.

A lock does not necessarily indicate an error. It may protect the structure against accidental deletion, leave only text editable or identify a template element. An area that cannot be selected is therefore not automatically a broken block.

Also distinguish an unexpected or invalid content message, which requires different troubleshooting. If a third-party block is missing after a plugin was deactivated, restoring it requires checking its provider. Removing a lock does not recreate that component.

Describe the intended action: move a paragraph, remove an image, reorganize a section or change the header on just one page. This precision avoids unlocking an entire pattern when changing text would suffice. Keep a screenshot of the selected block and its menu before intervening.

Find the block and its scope in List View

Open the relevant document, then List View through the document overview icon, usually at the top left. It shows the block structure. Expand available groups and select the item's name instead of targeting only its visual area.

Check whether you selected the paragraph, its parent group, a pattern or a template part. A group contains other blocks; moving it may move the entire section. Deleting that parent can also remove more content than the originally targeted image.

Record the padlock and menu labels. Some simplified interfaces do not show the entire structure: a view limited to text and images may indicate content-only editing. A group missing from that view does not prove it does not exist.

Finally, record the displayed document and template. A header visible while editing a page may belong to the shared template rather than that page's body. You must know where the change will be saved before using a command such as Edit original.

Preserve structure and confirm access

Keep a copy of useful text and media, plus a screenshot of block order. For a shared template or pattern change, arrange a recoverable backup of the affected database and files with the site administrator. A screenshot does not restore a complex block's settings.

First work on a control draft or staging when the change concerns several elements. A test copy must be separate from the live site; disable its notifications and external integrations if testing an interactive function.

Permission to write in a page does not necessarily grant access to its shared structure. Site rules may also restrict locking and unlocking by context. In multisite, a network-imposed theme or plugin may require its administrator.

Record the WordPress version and interface used. On WordPress.com and independent installations alike, menus may vary with available features. Keep the lock's initial settings: after the intended move, you can restore protection against accidental deletion without undoing the content correction.

Choose among the three possible protections

The first procedure concerns an individual lock visible in block options. It distinguishes protection against movement from protection against deletion. It suits a local block whose structural modification is authorized.

The second concerns a pattern and content-only editing. A pattern is a prepared set of blocks. It may preserve its layout while allowing text or image changes. Removing a lock from a single child does not necessarily restore structural tools.

The third concerns a template, shared element or site-imposed rule. It requires confirming scope and permissions before acting. A menu missing for an account may be intentional; adding a global setting to restore it would be disproportionate.

Start with observation and a minimal change on a copy. If the protection is not what you thought, undo the test and change procedures. Do not alternate HTML transformation, parent deletion and pattern detachment in an attempt to remove the padlock.

Approach 1: read both lock options

Select the exact block in List View, then open its toolbar's three-dot menu. If Unlock is available, open it to inspect the options. Labels may indicate movement locking and deletion locking.

These protections are distinct. A block may stay in place while permitting deletion, or be movable while remaining protected against removal. Record the initially active checkboxes before changing them. The padlock may remain displayed while at least one protection remains.

If you want to move the block, disable only movement protection and apply. If you need to delete it, first check its copy and disable only the corresponding protection. You do not need to lift both restrictions for one action.

When the interface offers to apply the choice to every block inside a container, leave that broader scope aside unless necessary. An entire section may combine different functions. If options are unavailable or the action remains impossible after applying, check editing mode and parent rules before continuing.

Make the targeted move or deletion

On the copy, move the block with arrows or available commands while checking its position in List View. Make one move, then inspect the result. A block moved within a group has not necessarily left that group; its visual location alone does not establish membership.

For deletion, check the selected element's name and children again. Use the block menu's intended deletion command. Do not erase the parent group to reach a child that remains protected: that changes the action's scope.

If the result is unsuitable, use Undo while available and verify that content returns. Do not assume reloading will undo an already saved state. After saving, a preserved copy or available revision may be necessary, following comparison.

Once the correction is achieved, restore intended protections through lock options. Check content, save and reopen the document. The expected result is the correct structure with remaining protections, not systematic removal of every padlock on the page.

Approach 2: recognize content-only editing

In some patterns, you can replace a sentence or image but cannot move columns, add elements or choose presentation settings. This editing mode protects layout. It may also simplify List View by hiding containers that do not directly hold text or media.

Select the pattern and look for a command such as Edit pattern or Edit, depending on the interface. If present and structural modification is intended, open it on the copy to recover blocks and their tools. Check that you are still in the correct occurrence or original.

Once in structural editing, make only the necessary correction. Keep a logical order of headings, paragraphs and buttons. A layout made more attractive on a large screen can become incoherent on mobile if blocks change groups.

If the command does not exist or restrictions remain active, do not add code to remove them everywhere. The mode may be defined by the theme, a pattern or a site rule. Identify its administrator and request access to the necessary scope rather than general freedom across all templates.

Check whether the pattern is synced

A synced pattern connects several locations to one original. Editing that original can update every place using it. Before choosing Edit original, determine whether the correction should be global or limited to this page.

If it should be global, work on a control copy with the required permissions, then prepare the original's update. Examine several representative pages and keep a recoverable version. Do not limit this check to the document from which you opened the pattern.

If only the local occurrence should differ, the interface may offer to detach or disconnect the pattern in its menu. This turns it into local blocks and breaks the connection to future original updates. It therefore requires a decision, not an automatic troubleshooting click.

Preserve the original and local content before this test. Detachment does not guarantee automatic reconnection. If you undo immediately, check the connection; after saving, prepare recovery from the retained copy or controlled reinsertion of the original. Never delete a pattern from the manager to remove just one page occurrence.

In List View on two control pages, select the pattern and record the original's name. A synced occurrence retains a reference to that original. After detachment, that occurrence's blocks belong to the page. If a field supports an override, you can also personalize its value while retaining the connection to the rest of the pattern. Use a paragraph without an override to compare the scope of shared editing and detachment.

On a working copy, insert the same original into pages A and B. In this example, its paragraph displays ‘Atelier à 10 h 30’. Add recognizable neighboring text to each page. Record the original's content, both occurrences and neighboring texts. If you inspect saved markup, linked occurrences carry the same ref attribute on the pattern block. Two identical on-screen paragraphs may come from two independent blocks.

Change the time in the working original and save it. Reopen A and B as a visitor. If both occurrences remain linked, they display the new time without further page edits. Before applying an original correction broadly, check other representative pages using it. Two test pages let you verify the mechanism on the copy.

To make A independent, open its List View and select the pattern itself. If the menu offers Detach, use it on A and check that the paragraph is editable within the page. If the option is missing, check the selection, permissions and pattern lock. Change A's local time, save the page, then change the original's time again. A must keep its local value and B must follow the original. Both neighboring texts must remain identical to their initial records.

Compare the following states in saved content and both public pages of your copy. These are expected results to verify, with no execution report provided here.

To undo an accidental shared edit, first restore the working original's content under the same identifier. Use a pattern revision if available or restore the exact saved fragment. Check the result on B. If A was detached, its local content must remain in place at this stage.

To also restore the connection in A, restore the version containing the original occurrence if that preserves your other changes. Otherwise, replace only detached blocks with an occurrence of the same original. Reopen both pages and check the time, connection and neighboring texts. Verify that a revision of A's content actually restores its reference and neighboring text before considering rollback complete.

Record whether you used editor commands or core functions to build the comparison. Technically replacing a reference with local blocks lets you examine data and rendering, but does not validate labels, permissions or the detachment path in your interface. Test these separately.

  • Initially, A and B should show 10:30 with the same reference. After changing the original to 11:00, both should adopt that value.
  • After detachment and a local edit, A should show 12:00 and B 11:00. A subsequent original change to 11:30 should update B while leaving A at 12:00.
  • After restoring the original, B should show 10:30 and A retain 12:00. After restoring the reference in A, both pages should show 10:30 and point to the same original. Neighboring texts must remain identical throughout all these steps.

Read the reference in saved markup

On the copy, open the code editor and compare the corresponding block in both pages without saving changes in this view. In staging, B retains the pattern reference. After detachment, A contains its own paragraph. The reference number depends on your site.

<!-- Page B : occurrence synchronisée -->
<!-- wp:block {"ref":1} /-->

<!-- Page A : paragraphe local après détachement -->
<!-- wp:paragraph {"className":"atelier03-horaire"} -->
<p class="atelier03-horaire">Atelier à 12 h 00</p>
<!-- /wp:paragraph -->

Approach 3: open the right template without changing everything

An element may be visible in the edited page while belonging to its template. This is particularly true of structural elements around the content. Check document settings and the template name before concluding that a local block refuses your action.

With a block theme and appearance permissions, Appearance, Editor, then Templates lets you find the relevant template. Template parts and patterns are also in the interface's designated sections. Do not open the first similarly named header without checking where it is used.

If you choose Edit original for a shared element, its scope may extend beyond the current page. For a one-page need, have the site administrator prepare an appropriate variant or assignment. Do not remove global protection to create that one-off difference.

Before saving, read the summary of modified elements. Keep other templates and content unchanged. If an error occurs, undo the targeted change or restore the preserved version. A complete template reset can erase other customizations and is not rollback limited to the block.

When the padlock belongs to the theme library

Under Appearance, Editor, Patterns, some theme-provided patterns may be protected against direct editing. This padlock concerns the supplied library definition; it does not necessarily indicate a movement lock on a paragraph in your page.

If the interface offers Duplicate and adaptation is intended, create an editable copy in your patterns. Give it a name distinguishing the theme original from your variant. This preserves the supplied reference and avoids rewriting files in a way that would be difficult to maintain.

Then check how to use this copy in the control document. Its presence in the library does not prove the current page already uses it. Compare structure and content before replacement, then keep the original accessible.

To undo the test, return to the preserved occurrence and remove only the now-unneeded variant after checking its uses. Do not delete a synced pattern assuming all its occurrences will remain intact. If the library or template does not offer the expected action, have the appropriate path confirmed for the theme and version.

Have site-imposed protection checked

If the account can edit text but cannot see lock commands, ask the administrator to compare the same block using an account authorized to manage structure. The goal is to identify the rule without sharing credentials or assigning a broader role to every author.

A theme, plugin or configuration can define permitted actions and which blocks may be inserted, moved or removed. Some protections pass through a container or template. The individual setting observed therefore does not necessarily describe the entire editing policy.

Provide the content type, template, block and intended operation. Request a limited exception or documented structural adjustment. The person maintaining the rule must preserve its configuration and check other uses before changing it.

Do not edit internal markup comments to remove every protection attribute. Do not disable a security component or an entire builder plugin to restore a command. Those actions could change permissions or presentation far beyond the affected block. If protection remains necessary, have the appropriate administrator perform the move.

Check structure and retain reliable rollback

After changing the copy, check List View and preview. The block must be in the correct group with useful text, links and media. Check heading order, mobile reading and keyboard access to buttons or links that moved.

Save and reopen the document. Verify that the correction persists and intended locks remain active. For a shared pattern or template, examine several pages using it; for a local change, confirm that other occurrences did not change.

If the result is wrong, return to the copy or an available revision after comparison. A post revision does not necessarily cover an independent pattern or changed template: restore the correct object without restoring the whole site for a block move.

Keep copies until validation and record the removed lock, its purpose and the protection ultimately retained. To request help, provide a sanitized screenshot, WordPress version, theme name and block provider. State precisely which action remains impossible; this record distinguishes intentional protection from an interface error.

Interpret attributes without removing protections in bulk

A maintainer can read block attributes to explain two different protections. The following fragment represents a Group that prohibits its own movement but permits deletion; its children may still depend on a template lock or their container's mode. This is a reading example, not an instruction to replace the existing block.

The lock.move and lock.remove attributes concern actions on this block. A parent's templateLock setting or editor policy may add other constraints. In particular, contentOnly provides content-limited editing: removing an individual lock is insufficient to recover every structural tool.

For authors, the free native Unlock menu remains the right approach when available and the change is intended. For maintainers, compare the block, parent and theme rule before modifying configuration. After a targeted move, restore intended protections and reopen the document. To undo, restore only the modified object; a page revision does not automatically restore a separate pattern original.

<!-- wp:group {"lock":{"move":true,"remove":false}} -->
<div class="wp-block-group">
<!-- wp:paragraph -->
<p>Texte de démonstration.</p>
<!-- /wp:paragraph -->
</div>
<!-- /wp:group -->

Sources and references

Use these references to check the features, requirements and limitations described. Reading documentation is not a practical test.

View 15 references

English translation of the reviewed French edition. Code examples retain their original identifiers, comments and output strings for reproducibility. Linked exercise files and original screenshots may contain French. No new practical tests or price checks are implied by translation.

Continue reading in English