New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sitewide Password Protection Bug #1001

Closed
marywarrington opened this Issue Sep 29, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@marywarrington

marywarrington commented Sep 29, 2016

Expected behaviour

I implemented sitewide protection, but have to enter the password every time I navigate to a new page on the site.

Actual behaviour

I'd like it to remember that I've already entered the password, and allow me to navigate freely for the session!

Steps to reproduce

  1. In system.yaml
protect:
  password:
    allowed: ['testpassword']
    form_url: /password-entry
  1. In routes.yaml
routes:
  /password-entry:
    template: password-entry
    protect: false
  1. Make a new template (password-entry.html)
            {{ protect:password_form }}
                {{ if no_token }}
                    <p>No token has been provided.</p>
                {{ else }}
                    {{ if error }}
                        <p class="error">{{ error }}</p>
                    {{ /if }}

                    <h3>Please enter your password:</h3>
                    <input type="password" name="password" />

                    <button type="submit" class="button">Submit</button>
                {{ /if }}
            {{ /protect:password_form }}
  1. I also pasted new code (provided by jason) into my statamic > bundles > protect > protectors > PasswordProtector.php.

    Server configuration

    Operating system: OSX

Web server: currently local. MAMP.

PHP version: 7.0.8

Statamic version: 2.1.11

Updated from an older Statamic or fresh install: Updated

@mikemartin

This comment has been minimized.

mikemartin commented Apr 21, 2017

Experiencing the same issue on a staging server. Sounds like it might be a known issue.
https://lodge.statamic.com/questions/2535-protecting-content-allow-logged-in#reply-1

@jasonvarga

This comment has been minimized.

Member

jasonvarga commented Jul 13, 2017

This is fixed in 2.6 - with a slightly different syntax. If you still need to use this feature, check out the docs for it when it's out.

@jasonvarga jasonvarga closed this Jul 18, 2017

@sicbe

This comment has been minimized.

sicbe commented Sep 11, 2018

I'm having the exact same "problem" with folder protection. I wanted to protect a folder with a password, but now I have to enter the password again for every page in the folder, while it's the same password for the entire folder. Is this the same bug, or is it intented to work that way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment