Setting up a print lock as requirement of DIN EN ISO 9001 certification
T
TheMet4lGod
That would be interesting. What I've been doing is duplicating the page in a different path that only editors have access to and mark it as unpublished.
F
Felicitas Pohl
TheMet4lGod Thank you for your idea. Unfortunately, this doesn't work for us. The documents must be visible to all employees, but versioned or with a print lock. This is about the requirements of DIN EN ISO 9001 certification.
T
TheMet4lGod
Felicitas Pohl What I meant was the draft updates are worked on in a different location with restricted access. Since the site stores all edits in the database, you still have the version history so to speak. I assign letters and dates to major revisions in a rev table on each page that needs it.
F
Felicitas Pohl
TheMet4lGod Thank you for your feedback.
Our goal is to make sure that no old revision is stored anywhere in the company. We have several hundred wiki entries where I would have to add a version table - we have no capacities to changes all pages.
It would be ideal to have a “print pages” option in the permission settings so that users can be granted or revoked permission. Or alternatively, that the date of the last change is automatically displayed in the print view.
T
TheMet4lGod
Felicitas Pohl That would be helpful. I'm also using Wiki.js as a quality manual of sorts at my company. In the interim, if you want to "disable" printing outright, you can inject some site-wide CSS code in the Administrative > Themes section as follows:
```css
@media print {
html, body {
display: none; /
hide whole page
/}
}
```
Of course, if someone knows how to access a browser developer console they can just copy and paste the code locally and render the page.
F
Felicitas Pohl
TheMet4lGod Thank you, but unfortunately I have too little knowledge to make such changes. I had hoped that it would be possible to set corresponding print settings without making programming changes in the background.