unverbuggt
unverbuggt
Hi, I was sponsoring squidfunk for two months, because without the `privacy` plugin from insiders risks are high to receive a GDPR warning letter from an attorney (at least were...
This plugin works by encrypting the page.content of a theme. The `blog` plugin generates a blog post not by filling page.content, but rather filling its meta information into a special...
Please try the current development version, this [patch](https://github.com/unverbuggt/mkdocs-encryptcontent-plugin/commit/d3db2e2aa6b194ece19eb731923ebe63f35e95d9) should also encrypt the `blog` pages. You need to configure the plugin like this (for material theme): ``` plugins: - blog -...
For my scripts I pipe the debug output ot tincd through [mtee](https://ritchielawrence.github.io/mtee/) (on windows) to add a timestamp. I think similar things could be achieved by the `tee` command in...
I didn't test with this plugin. Maybe we just need to re-call some javascript after decryption. I'll check. Edit: Did you make sure that the plugin order is correct? ```yaml...
The first-click behaviour is strange indeed. It doesn't trigger any javascript errors or such... I'd need to dig into how the glightbox plugin works to find the cause. It's probably...
Did you also try setting `webcrypto: true` or `esm: true` while enabling `navigation.instant`? This should fix being re-prompted for the password, however it won't fix the glightbox issue.
The new [Version 0.4.0](https://github.com/blueswen/mkdocs-glightbox/releases/tag/v0.4.0) of [mkdocs-glightbox](https://github.com/blueswen/mkdocs-glightbox) can be fixed by `reload_scripts` like this: ```yaml plugins: - glightbox: zoomable: true draggable: true skip_classes: - skip-lightbox - encryptcontent: reload_scripts: - '#init-glightbox' ```...
The javascript code of material is written in typescript. It needs to be compiled to javascript with nodejs to work in a browser. The process is explained [here](https://squidfunk.github.io/mkdocs-material/customization/#theme-development). The only...
Hi, yes, the limitation is 5MB of search index. I know this is only a bad hack... Currently, we also encrypt the `location` of a search entry (additional to `title`...