starred/BookStack
1
0
Fork 0
mirror of https://github.com/BookStackApp/BookStack.git synced 2026-02-09 19:06:13 +03:00
Code Issues 784 Packages Projects Releases 10 Wiki Activity

Column width on PDF export #1042

New Issue
Open
opened 2026-02-04 23:34:02 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 23:34:02 +03:00
Owner
Copy Link

Originally created by @ongmark on GitHub (Feb 18, 2019).

Describe the bug
When exporting to PDF, the output file does not respect the table column width as displayed in the page. It defaults to equal size for all columns.

Steps To Reproduce
Steps to reproduce the behavior:

  1. Create a table with uneven column widths. (i.e. Column 1 = ~50%, Column 2 = ~20%, Column 3 = ~20%, Column 4 = ~10%,
  2. Export page to PDF
  3. See effect on output PDF file. All columns will be 25% each.

Expected behavior
PDF output should respect the column width set on the UI.

Your Configuration (please complete the following information):

  • Exact BookStack Version (Found in settings): 0.25.1
  • Hosting Method (Nginx/Apache/Docker): Docker
Originally created by @ongmark on GitHub (Feb 18, 2019). **Describe the bug** When exporting to PDF, the output file does not respect the table column width as displayed in the page. It defaults to equal size for all columns. **Steps To Reproduce** Steps to reproduce the behavior: 1. Create a table with uneven column widths. (i.e. Column 1 = ~50%, Column 2 = ~20%, Column 3 = ~20%, Column 4 = ~10%, 2. Export page to PDF 3. See effect on output PDF file. All columns will be 25% each. **Expected behavior** PDF output should respect the column width set on the UI. **Your Configuration (please complete the following information):** - Exact BookStack Version (Found in settings): 0.25.1 - Hosting Method (Nginx/Apache/Docker): Docker
OVERLORD added the 🐛 Bug🎨 Design🏭 Back-End🚚 Export System labels 2026-02-04 23:34:02 +03:00
OVERLORD commented 2026-02-04 23:34:05 +03:00
Author
Owner
Copy Link

@kevin39 commented on GitHub (Aug 21, 2025):

Hi,
Is there any ETA for a fix ?

Thanks

@kevin39 commented on GitHub (Aug 21, 2025): Hi, Is there any ETA for a fix ? Thanks
OVERLORD commented 2026-02-04 23:34:08 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Aug 23, 2025):

@kevin39 No ETA. The tricky thing is that the issue itself is a fix for a prior (generally more problematic) issue.

@ssddanbrown commented on GitHub (Aug 23, 2025): @kevin39 No ETA. The tricky thing is that the issue itself is a fix for a prior (generally more problematic) issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 🎨 Design 🐛 Bug 🏭 Back-End 🚚 Export System
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#1042
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?