v2.1.3

   🚀 Features

• Long session, closes #13  -  by @johannschopplich in #13 (38b4b)

    View changes on GitHub

v2.1.2

No significant changes

    View changes on GitHub

v2.1.1

   🐞 Bug Fixes

• Plugin name for update check  -  by @johannschopplich in #11 (c9d7f)

    View changes on GitHub

v2.1.0

   🚀 Features

• Translated locked uri in multilang environment Closes #7 Closes #8  -  by @johannschopplich in #7 and #8 (017bb)

    View changes on GitHub

v2.0.0

   🚨 Breaking Changes

• Change config option namespace to johannschopplich.locked-pages  -  by @johannschopplich (eb749)

   ℹ️ Migration Guide

Rename your config options from kirby-extended.locked-pages.<some-key> to johannschopplich.locked-pages.<some-key>. That's it!

    View changes on GitHub

1.3.3

Notable changes

• chore: untrack composer.lock

1.3.2

Notable changes

• chore: add version number to composer.json for Kirby 3.6

1.3.1

Notable changes

• fix: hooks setup
• fix: check if page has been unlocked already

1.3.0

Notable changes

• feat: custom logout hook

Logout Hook

It is often helpful and good UX to provide the user a way of logging out. You can use a custom Kirby hook for this use-case.

Trigger the locked-pages.logout hook to clear the locked pages' session data. Once logged out, the user will have to enter the password again to visit the locked page.

kirby()->trigger('locked-pages.logout');

1.2.1

Notable changes

• refactor: plugin setup w/o vendor folder