How do you stop Adalo components from disappearing or auto-nesting?
Inspect the component tree for an unintended parent, remove the nested component, and align overlapping controls without dragging them into another container.
Short answer
Open the component tree and remove the missing component from any unintended list, rectangle, image, or group. For overlapping state controls, build each state separately and use keyboard movement for final alignment so dragging does not auto-nest one control inside another.
The intended outcome
Components remain visible and selectable because their parent-child hierarchy matches the intended screen layout instead of an invisible or overlapping container.
Start with the component tree whenever a control disappears after placement. Remove accidental parent relationships, keep intended containers explicit, and use keyboard positioning for overlapping controls that should stay siblings.
Requirements
- Separate image assets for the reacted and unreacted states
- A Boolean or relationship condition that identifies the active state
- Access to the screen’s component tree
Step by step
Step 1: Inspect the component tree
Expand the screen hierarchy and locate the missing component. Check whether it became a child of a list, rectangle, image, ellipse, or group that covers the drop area.
Step 2: Remove the unintended parent
Move the component out of the wrong parent in the component tree. If the parent is an obsolete invisible list or container, remove it only after confirming that no required content depends on it.
Step 3: Create two state containers
Add one rectangle for the unreacted state and another for the reacted state. Put only the matching image inside each rectangle.
Step 4: Set opposing visibility rules
Show the unreacted rectangle when the state is false or absent, and show the reacted rectangle when the same state is true or present.
Step 5: Wire both tap actions
Give each visible rectangle the appropriate action: one sets or adds the reacted state, and the other clears or removes it.
Step 6: Assemble away from the overlap
Prepare the two rectangles in separate areas of the canvas so dragging an image or rectangle does not drop it fully inside another container.
Step 7: Align with keyboard movement
Select each finished rectangle and use arrow keys, with Shift plus an arrow for larger moves where supported, until both occupy the same coordinates. Verify their sibling order in the component tree.
The underlying logic
Adalo lists, groups, rectangles, images, and ellipses can act as parents, so a component dropped into their bounds can change hierarchy instead of remaining a screen-level sibling.
Adalo treats rectangles and images as containers when another component is dropped fully inside their borders, so drag-and-drop placement can silently change the parent-child tree.
Two sibling state containers keep each image, visibility rule, and tap action independent while still allowing both controls to occupy the same visual location.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| The record that owns the button state | A Reacted Boolean or equivalent state property | Optional relationship to the user who reacted when reactions are user-specific |
What still needs checking?
- This is a forum-native answer with no original Adalocado video; current documentation confirms that rectangles act as Auto-Group containers when components are dropped fully inside them.
Common failure modes
Testing checklist
0 of 9 checked on this device
Current limitations
- Keyboard positioning is a community workaround confirmed in the source thread; exact shortcuts and component-tree behavior can vary between builder versions.
- Current Adalo documentation confirms rectangle Auto-Groups and how to remove nested components, but Adalocado has not reproduced this exact custom-button stack in a current project.
- The supporting disappearing-button topic was resolved by its author in a later unmarked post. The accepted marker points to an earlier exploratory reply, and Adalocado has not reproduced that exact invisible-list setup.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts, not endorsements or independently reproduced results.
Issues with stacked images nesting inside each other
The maker confirmed that separate rectangles plus keyboard positioning prevented unwanted nesting and allowed a working custom-art button.
Boundary: The thread reports a builder workaround rather than a dedicated lock-layer or disable-nesting feature.
obrienpaule (question and accepted confirmation), with Ali-Bazzi and Victor · May 2026
Buttons Disappearing
The author found an invisible list covering the affected area. Deleting the unused list stopped newly placed buttons from disappearing.
Boundary: The concrete fix appears in a later author post rather than the accepted reply and may not explain every disappearing-component symptom.
ThunderBlade (question and documented fix) · January 2026
Sources and status
This page was last reviewed on Aug 26, 2026. Its current status is Documented from current sources.
Verification owner: Adalocado editorial. Next review: Oct 14, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Automatically organized and maintained by the Adalocado editorial team under the editorial and verification policy.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
