mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 00:59:39 +03:00
Follow Page Bug When Page is Moved to Non-Followed Book #4364
Closed
opened 2026-02-05 08:40:29 +03:00 by OVERLORD
·
6 comments
No Branch/Tag Specified
development
further_theme_development
l10n_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label
🐛 Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#4364
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mschoon85 on GitHub (Dec 13, 2023).
Describe the Bug
Hi @ssddanbrown ,
I might have found a bug. Through the API, I imported a DOCX document into Book A, which I am following, and I receive emails whenever there are changes within the book. Later, I moved the page to another book, let's call it Book B, which I am not following. Surprisingly, I received an email notification when someone made a change to that page, even though it's now in a book I'm not following. In the screenshot below, you can see the details on the page itself. It appears that I am not following it (apologies for the Dutch language), as the "follow" button (volg) is available, and the top details do not indicate that I am following the page.
Kind regards,
Michel
Steps to Reproduce
Enable Notifications for Target Book: Ensure you are following the book where you intend to upload the document. Verify that email notifications are properly configured (e.g., SMTP settings).
Upload Document via API: Upload a DOCX document to this book through the API. Note: The issue might also arise when creating a new page manually, but this has not been tested yet.
Select a Non-Followed Book: Identify a book that you are not currently following and transfer the page to this book.
Test Notification Trigger: Modify the page within the book you're not following. Observe if you receive an email notification regarding this change, which will indicate whether the issue persists.
Expected Behaviour
I would anticipate not receiving an email notification, as the page has been moved to a book that I am not following. Furthermore, the page's details themselves indicate that I am not following it, reinforcing this expectation.
Screenshots or Additional Context
No response
Browser Details
MS Edge
Exact BookStack Version
23.10.4
@ssddanbrown commented on GitHub (Dec 13, 2023):
Hi @mschoon85,
Could you also confirm the notification settings you have in "My account" > "Notification Preferences". Just want to check that these are not the cause.
@mschoon85 commented on GitHub (Dec 13, 2023):
@ssddanbrown
It appears that I am currently following only one book, which is 'Book A' as mentioned in my problem description. 'Book B', on the other hand, is not listed on this page.
@mschoon85 commented on GitHub (Dec 13, 2023):
Ah, I've just noticed that these settings are configured to notify me about pages that I own. This could be the reason behind the issue.
@mschoon85 commented on GitHub (Dec 13, 2023):
I've manually updated the owner through the permissions settings, so I don't expect to receive any more emails regarding this issue.
@ssddanbrown commented on GitHub (Dec 13, 2023):
Yeah, if you're the owner that you're getting notifications due to that general notification preference.
@mschoon85 commented on GitHub (Dec 13, 2023):
Thank you! We can now close the ticket as it's not a bug.