Publisher 2.6.0/2.6.2 does not show/paint off page text frames inherited from master page

[User 691]

The issue is described on the image attached. From version 2.6.0 I cannot see text of text frames that are off page and inherited from master page. If I manage to make the text visible by tying additional characters in the box, the text is only visible until I close the file.

Windows 11, X64. Turning off hardware acceleration has no effect.

Master frame issue.afpub

[Oufti]

FWIW, I see the same on my Mac [screenshot 1]. 

I also notice that the off-page text frame is not displayed in the Layers panel (= Calques), even when I've typed something into the text frame [2], until I've toggled to Master frames (= Maquettes) and back to Pages [3]. 

[MikeTO]

I don't think this has been reported before.

[User 691]

I now discovered that the issue does not only affect text frame, but any object (like rectangle) that is off the page on master page is not displayed on pages that inherit from the master page. Such objects are not displayed in layers list of the inherited page! This is bad, I must revert back to 2.5.

[Affinity Info Bot]

The issue "Master page pasteboard content no longer appears on page" (REF: AF-6420) has been fixed by the developers in the latest beta build (2.6.3.3273). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

This fix has been reverted by the developers as it introduced new problems. An alternative fix will be sought.

[Affinity Info Bot]

The issue "Master page pasteboard content no longer appears on page" (REF: AF-6420) has been fixed by the developers in the latest beta build (2.6.4.3439). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.