Closed guise closed 1 year ago
Hi,
I've set the "version3" branch als main branch lately, because I want to release v3.x soon, which will bring features like password_inventory
. But pip is still on 2.x, so If you want the documentation for the latest 2.x release, please check here.
However, there are pre-releases available to give a try, but I already found a sack full of bugs yesterday, so the latest pre-release is not on par, yet. So best do this:
pip install wheel #not sure if other packages are needed
git clone https://github.com/unverbuggt/mkdocs-encryptcontent-plugin.git
cd mkdocs-encryptcontent-plugin/
python setup.py sdist bdist_wheel
pip install --force-reinstall --no-deps dist/mkdocs_encryptcontent_plugin-3.0.0.dev3-py3-none-any.whl
That worked perfectly, thank you!
Would it be advised to switch back to a pip
install once v3 is released? If so, what would be the best way to do so?
All you need to do is pip install --upgrade mkdocs-encryptcontent-plugin
once v3 is released.
Hi — as per title
I've stripped my project back to barebones trying to debug and figure out where I'm going wrong, but i've hit a brick wall.
mkdocs.yml config:
test.md
Things are working fine using
password: test
as a meta tag in the test page, or setting aglobal_password: 'test'
in mkdocs.ymlHowever, setting
level: secret1
orlevel: secret2
in test.md meta tags does nothing!ENV TESTVAR
also works fine when using it to set the page title.I feel like i'm going mad missing something obvious!?
I'm running:
3.11.4
1.5.2
from /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/mkdocs (Python 3.11)