daledupreez

I've started working on a fix in 174382-ghe-Automattic/wpcom.

Noting that I deployed 174382-ghe-Automattic/wpcom a little while ago, but we still need https://github.com/Automattic/wp-calypso/pull/100536 deployed to get this fully resolved.

@aneeshd16, after your deploy of #100536 yesterday, do you think we can close this issue?

I managed to reproduce the issue @sixhours encountered, and I think I tracked it back to the seemingly innocuous line of code on line 40 below: https://github.com/Automattic/wp-calypso/blob/1112c9618ed8a8d17a8dea97e8f55678ab8c458c/client/landing/stepper/declarative-flow/internals/steps-repository/launchpad/index.tsx#L40-L46 What I am...

Noting that I deployed this change to production in D159963-code.

@merkushin, Serenity can also step in to tackle this aspect of the refactor so you can focus on exposing the introductory offers.

@lsl, we manually launch the site via this block of code after migrations complete: fbhepr%2Skers%2Sjcpbz%2Snflap%2Qwbof%2Svapyhqrf%2Szvtengvba%2Szvtengvba%2Qpyrna%2Qhc.cuc%3Se%3Qp91226sq%23178%2Q200-og Note that function is called against the WordPress.com data, and not the Atomic site, as...

@miksansegundo and @lsl, I think we need to be specific about terminology: * The code @miksansegundo linked to in [this comment](https://github.com/Automattic/wp-calypso/issues/93571#issuecomment-2310111144) is specific to normal Atomic transfers between Simple and...

@lsl, I think the issue also revolves around the state of the Atomic site, which is where the logic for (not) showing the Coming Soon pages exists, mostly in https://github.com/Automattic/jetpack/blob/5281706f1082683bc3cf22149e14011a13034d6a/projects/plugins/wpcomsh/private-site/private-site.php....

Thanks for reporting, @niranjan-uma-shankar! I'll take a look at both items -- @Automattic/nexus have also been working on this page.