Table of Contents
Problem Description #
On cart or checkout page, when using popups for notices (e.g. coupon added/removed, error message), the popup appears briefly then disappears too fast; sometimes removing a coupon also hides the coupon input field, preventing user from re‑entering a code.
Common symptoms #
- Popup shows for ~1‑2 seconds, then vanishes before user can read it. WordPress.org
- After removing a coupon, the coupon input box disappears completely from checkout/cart page. WordPress.org
Cause #
The plugin’s default JS behavior may auto‑close notices or hide elements after certain events. In some cases, the “auto‑close” or “dismiss on click” logic may run too aggressively after AJAX events. Also, conflicts with theme or other JS scripts may trigger unintended hiding of coupon inputs. In the cited thread, the user manually modified front.min.js to fix the issue.WordPress.org
Solution (step‑by‑step) #
- Check plugin settings, see if there is an “auto‑close after X seconds” or “dismiss on click” option; disable or increase the delay so popups remain long enough.
- Test with default WooCommerce + plugin setup: temporarily switch to a default theme and disable other plugins (especially caching / optimization / checkout‑customizing plugins). This helps to rule out JS conflicts.
- Check AJAX handling: If your site uses AJAX for coupon application/removal, ensure that the plugin handles dynamic content updates properly.
- If field disappearance persists: as a workaround, add a custom JS snippet that re‑renders the coupon field after AJAX events, or contact plugin support for an official fix.
- Clear caches: especially if you use caching or minification plugins, ensure front.min.js isn’t cached or old.
Prerequisites #
- Plugin version 1.3.4 or later (issue reported on 1.3.4). WordPress.org
- Access to theme/plugin settings; optionally, ability to add custom JS or deactivate/minimize conflicting plugins.
Additional Notes #
- Consider disabling “auto‑close” for checkout or coupon‑related popups, better UX to let user read message and act.
- If you make manual JS edits, keep track of them (child theme or custom plugin) so updates don’t override.
