[GH-ISSUE #8573] [Bug] When creating a new DB page via a linked view of a DB using page models, a "double window" appears making data entry very confusing #3918

New issue

Open

opened 2026-03-23 21:34:08 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 21:34:08 +00:00

Owner

Originally created by @Ray0m on GitHub (Mar 13, 2026).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8573

Bug Description

When creating a new DB page via a linked view of a DB using page models, a "double window" appears making data entry very confusing.
This is a strange problem to describe to please view the following video demonstrating the issue : https://www.youtube.com/watch?v=BwcVOjSKIBo&t=386s

How to Reproduce

create a page model in any DB
create a linked view of said DB
in linked view, click the 'new" button to create a new DB page using the new page model
notice that multiple "new page" pop ups seem to open one over the other
give a test name to your newly created page and save
notice that you have now editing a second "new page" that was hidden underneath the first
give a different test name to this new page
go to your DB to find your newly created pages
you should only be able to find the last page you created, all of the first ones should have disappeared

Expected Behavior

it should be have is "normal" :
1 page should open and it should be saved normally

Operating System

windows 11

AppFlowy Version(s)

0.11.4

Screenshots

No response

Additional Context

No response

Originally created by @Ray0m on GitHub (Mar 13, 2026). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8573 ### Bug Description When creating a new DB page via a linked view of a DB using page models, a "double window" appears making data entry very confusing. This is a strange problem to describe to please view the following video demonstrating the issue : https://www.youtube.com/watch?v=BwcVOjSKIBo&t=386s ### How to Reproduce 1. create a page model in any DB 2. create a linked view of said DB 3. in linked view, click the 'new" button to create a new DB page using the new page model 4. notice that multiple "new page" pop ups seem to open one over the other 5. give a test name to your newly created page and save 6. notice that you have now editing a second "new page" that was hidden underneath the first 7. give a different test name to this new page 8. go to your DB to find your newly created pages 9. you should only be able to find the last page you created, all of the first ones should have disappeared ### Expected Behavior it should be have is "normal" : 1 page should open and it should be saved normally ### Operating System windows 11 ### AppFlowy Version(s) 0.11.4 ### Screenshots _No response_ ### Additional Context _No response_

mirror commented

2026-03-23 21:34:08 +00:00

Author

Owner

@richardshiue commented on GitHub (Mar 16, 2026):

Hi @Ray0m, indeed we try as much as possible to fill in the cell contents so that it may satisfy the current filter criteria. And our intention is that if the new record with its filled cell contents doesn't satisfy the filter content (meaning it won't be shown in the grid or which view you have), that it will open the page in a popup so you don't get the illusion that nothing has happened.

The problem is, when we try to create a record using templates, it also opens the page in a popup. My guess is that this is where the issue is stemming from. We will look into this issue and hope to come up with a fix soon.

@richardshiue commented on GitHub (Mar 16, 2026): Hi @Ray0m, indeed we try as much as possible to fill in the cell contents so that it may satisfy the current filter criteria. And our intention is that if the new record with its filled cell contents doesn't satisfy the filter content (meaning it won't be shown in the grid or which view you have), that it will open the page in a popup so you don't get the illusion that nothing has happened. The problem is, when we try to create a record using templates, it also opens the page in a popup. My guess is that this is where the issue is stemming from. We will look into this issue and hope to come up with a fix soon.