Checkout button problem

[Kiwart]

Hello I need developer specialist for my button bug.

When clients proceed from cart drawer to cart - the place order button its there , disappears , then come back.

Can I know how to fix it , if you need the main-cart-footer.liquid i will send it.
But please help me solve it because the opening is soon and I try my best to look professional.

site: privateviewscreen.com
password: 1 (one digit)

[devcoders]

Hi @Kiwart

Could you please send me collaborator access so I can fix this issue directly in your theme?

Best regards,
Devcoder

[Maximus3]

Looks like you have a conflict between Parcely and Easify.

1. Parcely is watching the cart area.
2. Easify is applying a class to the checkout button to change visibility of button for purposes of loading product options.
3. This triggers a re-scan in Parcely. And it just loops over and over infinitely.
4. Dev console is being spammed endlessly with “observer” logs from cartv2.js every second.

[Kiwart]

I tried to disable it , but the problem is still there

[Maximus3]

By design, these 2 apps each control the checkout button, but for different reasons.

Parcely controls it because it wants you to choose a pickup point first. Easify controls it to ensure the product options have been fully loaded before checkout. Both cannot co-exist in their current state, they are just playing tug-o-war.

I would check the app settings, or uninstall one of the apps. You could also try to force it with css. This would go at the bottom of base.css or theme.css

button#checkout.tpo-btn-checkout,
.cart__checkout-button[name="checkout"],
#checkout {
    display: inline-block !important;
    pointer-events: auto !important;
    opacity: 1 !important;
    visibility: visible !important;
}

[tim_1]

Maximus is spot on with diagnostics.
Making your checkout button always visible/clickable is an option, but it will prevent the apps from working the way they were designed.

---

Usually, the goal is to shorten the path your visitors have to follow to become customers.
You have a drawer cart, but also a cart page – does this extra step really necessary/worth it?

[Kiwart]

You are right but I like the drawer but I can’t have Parcely app to choose postbox - adress of shipping it must be in cart.

So I redirect from drawer to cart where there will be Parcely app for shipping methods

[karanraval]

This looks less like a theme bug and more like a JavaScript app conflict on the cart page.

From the symptoms (button appears → hides → reappears), one script is likely re-rendering main-cart-footer or toggling the checkout CTA after another app modifies the cart DOM.

Since Parcely and Easify were mentioned, I’d test in this order:

1. Disable one app at a time and retest cart drawer → cart page flow.

2. Check for duplicate event listeners / MutationObservers firing repeatedly.

3. Inspect whether the checkout button gets a temporary hidden class (hidden, opacity-0, display:none) then removed.

4. If confirmed, move the app injection point or exclude the checkout button container from observer scans.

Quick temporary fix before launch: debounce the observer or stop both apps from targeting the same cart footer node.

If no-code launch is urgent, ask whichever app owns the checkout logic to whitelist the cart footer. This is usually faster than editing theme files last minute.

[mastroke]

this is happening because of re-render issue by AJAX call,
see if you can edit cart form like this

<form action="/cart" method="post" id="cart">
  <button type="submit" name="checkout" class="cart__checkout-button button">
    🔒 Place Order
  </button>
</form> de

and you can also use css to fix the layout stick to that position only

.cart__checkout-button {
opacity: 1;
transition: opacity 0.3s ease;
}

.cart–updating .cart__checkout-button {
opacity: 0.5;
pointer-events: none;
}

Let me know if this working for you else will provide other solution as well.

thankyou

[Maximus3]

You could also contact the app developers for help. Easify has reps in here.

[markjane]

Hey,
Thanks for sharing the details I understand how important this is, especially with your launch coming up.

What you’re describing (the “Place Order” button briefly disappearing and reappearing) is usually caused by a JavaScript re-render or cart validation script triggering when the page loads or updates. This often happens with cart drawers, dynamic sections, or apps that modify the checkout/cart behavior.

A few quick things I’d like to check to pinpoint it properly:
– Which theme are you using?
– Have you recently added any cart/upsell/discount apps?
– Does the issue happen consistently or only on first load?

Yes, please go ahead and send over your main-cart-footer.liquid file that will help a lot. I’ll review it and show you exactly what’s causing the flicker and how to fix it cleanly.

We’ll get this sorted so your store looks polished before launch