For browsing the pages, you can simply open them. I hope you login with admin user (that has all the permissions) and you would be able to edit as well. You can install the same package on publish instance (through crx) to browse in publish

Try with this: https://github.com/apache/jackrabbit-oak/tree/trunk/oak-runHope this helps.

@mmbb110 Thanks the trick worked

Download aem-guides-wknd.all-0.0.6-classic.zip and go to CRX packmanager.Upload and Install this package there. Refer this link: https://experienceleague.adobe.com/docs/experience-manager-65/administering/contentmanagement/package-manager.html?lang=en#how-to-work-with-packages

Please share more details around the personalization done in the email and the workflow/ segmentation steps. The issue would indeed be related to personalization/ customization as I don't seem to face the same challenge.

@AndrewKriz  Detailed information around rendering in different email clients, is dependent on the license agreement.https://experienceleague.adobe.com/docs/campaign-standard/using/testing-and-sending/preparing-and-testing-messages/email-rendering.html?lang=en#email-rendering-report-descriptionHope ...

Email Rendering is disabled when creating a new Test Profile as "The Email rendering use is read-only. Test profiles with this use are only available out-of-the-box in Adobe Campaign" as per documentation. Moreover, Email Rendering is to test an email with various email clients. In the Email Preview...

@mmbb110  Below part seems to be incorrect in your email:data-nl-expr="context.targetData.GENERIC06 === 'Y'"How did you add this condition? Were there any manual changes done in source?

I have created a new test profile (Profiles & Audiences > Test Profiles) but I do not see this or any new test profile created under the 'Test Profiles' section to 'Change profile' and 'Preview' email in Email Designer.Following these steps: https://experienceleague.adobe.com/docs/campaign-standard/...

I don't think it's related to advanced mode. It this text stays after removing the advanced condition, it could be something else. From the image it looks like you've combined the length > 2 with !== '' which seems to be creating the issue.