mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Restore from recycle bin failed #2165
Closed
opened 2026-02-05 03:10:22 +03:00 by OVERLORD
·
8 comments
No Branch/Tag Specified
development
l10n_development
further_theme_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
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#2165
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 @dusatvoj on GitHub (Mar 18, 2021).
Describe the bug
Somebody deleted a page. I've tried to restore it (Recycle bin -> restore). Now: page isn't in recycle bin even restored (can't find that page)
Steps To Reproduce
Steps to reproduce the behavior:
Successfully restored pages: 0Expected behavior
Successfully resotred page with link in clipboard / smth like this.
Screenshots
N/A
Your Configuration (please complete the following information):
0.31.2(after that upgraded tolatest)v7.4.13mod_phpAdditional context
Add any other context about the problem here.
@ssddanbrown commented on GitHub (Mar 19, 2021):
Hi @dusatvoj,
There are some edge cases that can cause issues that we've fixed in more recent patch releases. I'm not sure what the
latestin your issue refers to, but it's worth updating tov0.31.8to help prevent these.It may be the case you hit an issue that prevented the permissions for the page being built correctly.
You could attempt to regenerate these, after updating, by using the
php artisan bookstack:regenerate-permissionscommand: https://www.bookstackapp.com/docs/admin/commands/#regenerate-access-permissions@dusatvoj commented on GitHub (Mar 19, 2021):
Hi @ssddanbrown ,
Yep, I mean latest release ... it's
0.31.8. I've tried to regenerate permissionsphp artisan bookstack:regenerate-permissionsbut the page looks lost. Maybe it's caused by some bug inv0.31.2(the version I've tried to restore page). There's in DB stilldeleted_atdate. Is that correct? (Maybe there's just something stuck in DB ... IDK)@ssddanbrown commented on GitHub (Mar 19, 2021):
Hmm, No, That's not correct if it's been restored.
Setting the
deleted_atdate tonullshould make it re-appear.@ssddanbrown commented on GitHub (Mar 19, 2021):
@dusatvoj As an extra note, is the parent book/chapter definitely not also in the recycle bin? That could also cause this behavior.
@dusatvoj commented on GitHub (Mar 19, 2021):
I've set page's
deleted_attonulland it's restored now.Yes, It was our fault. Our co-workers told me that they deleted a page but they deleted a whole book. I've tried restore a page and bookstack told me
success: 0and page dissappeared from trash but not restored.Is there a possibility (if it's not done yet in
v0.31.8) to leave page in trash if restore wasn't success? This was confusing 😊@ssddanbrown commented on GitHub (Mar 19, 2021):
Thanks for confirming @dusatvoj.
These edge-case scenarios get tricky. The page has been restored itself but the delete is still inferred by the parent. I'm pretty sure I handled this by showing a message when you attempt to restore an item in such a scenario:
@dusatvoj commented on GitHub (Mar 19, 2021):
Oh, I've missed the message under restore button.
Thank you for your time.
@ssddanbrown commented on GitHub (Mar 19, 2021):
No problem! I'll keep this in mind though, If we start to see many other similar reports I'll look to tweak the user experience/feedback to make these more obvious.