Skip to content
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

Logged in user can see gift code having not purchased any #538

Closed
mfritzsche opened this issue Apr 8, 2015 · 2 comments
Closed

Logged in user can see gift code having not purchased any #538

mfritzsche opened this issue Apr 8, 2015 · 2 comments

Comments

@mfritzsche
Copy link

I have the latest build installed with the Gift/Redemption Code bug fix and I am seeing that a member I created (for testing purposes) that has not purchased any gift codes is seeing a valid gift code on a page that generates a gift code and is protected by specific post/page access restriction. Is there some setting that I may be missing that is allowing a logged in member who has not purchased a gift code to be able to see this Redemption Code?

The page with the redemption code has this form code:
[s2Member-Gift-Codes discount="27.00" quantity="1" one_click="/member/redeem/" /]

The redemption code post id is 12103 and I have added that to the Specific Post/Page Access Restrictions line (comma separated list -- 12103,12130 -- as there are other pages that are protected).

Again, a brand new member who has NOT purchased redemption codes can see a valid redemption code on the page mentioned above.

image

image

@ioerjfoige0439i
Copy link

Interested in hearing an update on this one too and if it's a bug or some other error :)

@jaswrks
Copy link
Contributor

jaswrks commented Apr 19, 2015

@mfritzsche writes...

Again, a brand new member who has NOT purchased redemption codes can see a valid redemption code on the page mentioned above.

I was unable to reproduce this. When you tested, did you delete all browser cookies beforehand? Once you purchase a Specific Post/Page, s2Member sets a cookie in your browser upon clicking the Specific Post/Page Access Link. Thus, logging out, registering a new account, logging out again, then testing it all over again; none of that will delete the Specific Post/Page Access cookie, because this sort of access is not dependent upon a user being loggged in.

Clear cookies and try again. If problem still occurs, please report back. Thanks!

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

No branches or pull requests

3 participants