Have feedback for the Replo team?

Share how Replo can make their product better for you and your team.

"Set as homepage" toggle and "publish page" steps

Hello there —We just tested that whenever we release a new Shopify theme, the theme push is causing the "set as homepage" toggle to turn off on its own. Every time we need to release a new theme, we need to do the following steps: 1) turn on that toggle back on, and 2) hit “publish page”. These steps are adding complexity onto a process that should be done quickly in order to don’t disturb users. Before, we didn’t need to do step 1, but now it has become clear in the latest theme releases that we need to do both steps in order for our homepage to be visible. It’s also concerning since our devs sometimes need to push new themes for hot fixes, and my team may not be around. If they do, because the toggle "set as homepage" is turning off automatically, this is going to cause the Homepage to go dead every time they do this when my team isn’t around to support them. I think these two steps in Replo are unnecessary and do not consider clients that new to release new themes quite often, like our company. I’d like to request that these two steps be eliminated so a smoother process can be in place. Ideally, any time a new shopify theme is released, Replo should stay as is and not break the connection to the homepage —just like it does with its other pages. All Replo pages are always fine when a new theme is pushed, except for the homepage, which is strange since it’s the most pivotal page. Thank you!

An Anonymous User 2 days ago

💬 Replo

Native Event Access in "Run JavaScript" Interactions

It would be great having feature that exposes the native browser event object within Replo’s On Click → Run JavaScript interactions to allow developers to access critical data like event.target. Currently, because this object is inaccessible, users struggle to isolate JavaScript actions when a page contains multiple identical or duplicated sections, such as in A/B testing scenarios. By allowing the script to identify exactly which element was clicked, developers could use simple logic like.closest() to ensure actions are "siloed" to the correct container, preventing accidental triggers in hidden or duplicated sections. Implementing this change would eliminate the need for cumbersome global event listeners in Custom HTML blocks and enable the creation of truly portable, "smart" components that function reliably regardless of where they are placed on a page.

An Anonymous User 3 months ago

💬 Replo