David Hunt

Hi,
A last bit of feedback before the close of 2012!

I can access the download if I’m a paid up member here http://presspresse.com/activity/
( http://presspresse.com/members/oksoadmini/activity/favorites/ )

However, if I try and access the download via Forum post @ http://rockstarraw.com/forums/topic/welcome/
( http://rockstarraw.com/?s2member_file_download=restore/restore.pdf&s2member_file_download_key=allowphp%20function=1 )

I get 503 ( Invalid Key ): Sorry, your access to this file has expired. Please contact Support for assistance.

So, as far as a multisite setup is concerned, with activity streams and RSS, the protection is not making sense to me.

Thanks for all your help in 2012!

There appears to be a flaw in the BBPress permalink structure when trying to protect a Forum with uri based restriction.

If I set up url based restriction to ‘forum-name’
domain.com/forums/forum-name/

as soon as a user is aware of a thread eg. domain.com/forums/topic/thread-name
the url restriction set in ‘forum-name’ is bypassed.

There’s no way to use url restriction to set a top level protection and have all threads protected within the forum-name structure.

It’s also conflicting with the logic of the breadcrumb path which shows the correct structure.
Home › Forums › Forum Name › Topic
which would allow the uri restriction to be effective.

Am I missing something?

Thank you.

The only thing I’m still a little unsure of how to utilise the restriction in this scenario. How does the buy now option play with the restriction control? If a purchaser gets the link eg http://tinyurl.com/dynamiclink are they then also impinged by the download restriction for level 0 user? eg.

File Downloads ( Level #0 Or Higher ): 1 every 30 day(s).
Only this many unique downloads will be permitted every X day(s), at Level #0 or higher.
* To allow UNLIMITED downloads, use: 999999999 ( i.e. 999999999 = unlimited ). ETC.

Is their key allowing 1 X level 0 access + (

s2member_file_download_key("example-file.zip") = a site-specific hash of: date("Y-m-d").$_SERVER["REMOTE_ADDR"].$_SERVER["HTTP_USER_AGENT"].$file

), so as soon as they download 1 pdf they’re restricted from any further downloads?

The main thing is that I would like to understand is how I’d use this simultaneously with a member level branch that might allow a specified number of downloadable treats based on the subscription model.

• This reply was modified 4 years ago by  David Hunt.
• This reply was modified 4 years ago by  David Hunt.

Code Snippets
Edit Snippet ID: 1
Shortcode: [php function=1]
all snippets automatically start with

<?php
echo s2member_file_download_key("merry_ebook.pdf"); ?>

yields: http://deliciously-raw.co.uk/merry-ebook/
http://deliciously-raw.co.uk/?s2member_file_download=merryandbright/merry_ebook.pdf&s2member_file_download_key=ea0d11a41fad1318a09cd636c401755d

BUT, if I refresh page should I get the same key? eg. s2member_file_download=merryandbright/merry_ebook.pdf&s2member_file_download_key=ea0d11a41fad1318a09cd636c401755d

user details:
cristian cristian+testing@xxxxxxxx.com Administrator

can I mail password if you haven’t received the invite?

• This reply was modified 4 years ago by  David Hunt.
• This reply was modified 4 years ago by  David Hunt.

great, I look forward to the kb.

To create some consistency and not dupe pages, I’ve decided to go with two top level pages, using pro forms, which works beautifully for logged in and logged out/non members;

s1>s2 http://domain.com/pro-registration/
s2>s3 http://domain.com/proplus-registration/

I’ve nested that under the Pricing tab, so hopefully user will be familiar with the member levels and respective privileges. Nearly there.

Hey Bruce, thanks for the heads up.

So, I get we can use the S2 variables in an edited version of the redirect in our current hack. Can you take a moment to advise how I can edit options page, or other bespoke redirect page to facilitate the desired ‘land on specific’ S2 pro upgrade form.

Does it simplify the issue if I use the hack to land on new bespoke pages, just with one necessary pro form for desired upgrade, rather than use the /opions/ page?

Hi Bruce,
I’ve tested the feature and I still get 404. I have a test user who has joined 7 blogs. If I set S2 Level 1 to 8 I get /create/, if I set it back to 7, I get 404.

Id tried to bite into the code using a redirect @line31 in create.php but didn’t have any success with wp_redirect( ‘/microsites/create’, 302 ); exit;

OK, next step?

ok, can I have some help here then. Is there a way to get S2 to throw up anything that I can catch or use to redirect members either to the S2 options page or a custom pro form to upgrade their S2 membership? It seems a bit crude that S2 promotes the support of ‘Maximum Blogs Allowed’, but user gets a 404 when the allocation is exceeded. How have other customers responded to this? Any leads appreciated.

*I know I’ve mentioned this before, I’m getting this from debug:
NOTICE: wp-content/plugins/s2member/includes/classes/cache.inc.php:97 – Undefined variable: cache_needs_updating

• This reply was modified 4 years, 4 months ago by  David Hunt.

Hi Jason & Cristian, can you task me with a lead on making some progress on this. Kind regards, David

Hi Cristian,
Just to let you know I’ve now tested the config on two separate sites, the same issue remains…

for an S2 Level 1 member (when the membership level 1 blog allowance is set to 0) I get 404, not a redirect to options.

for an S2 member (who has exceeded their membership level blog allowance) I get 404, not a redirect to options.

I think the thing to do now is get a clear instruction as to what the software should do in these two scenarios.

Thanks. David

Hi Cristian,
I’ve cracked one issue after testing hypothetical S2 Level 2 scenario, and found the system was working as expected for L2 users. This led me into looking at wp capabilities and flushing everything clean.

re: ‘Especially if you have two URI strings match at different levels: /microsites/create/ will match /microsites/create/ but also /microsites/.’

This is not the case, I can have a logged out user get redirect for /microsites/
and have a L0 have access to /microsites/ but not /microsites/create/
and have a L1 have access to /microsites/create/

ie. It appears that as far as S2 buddy restrictions are concerned /microsites/ & /microsites/create/ are two distinct entities, which is great!

My original error was coming from a faulty WP capability records. As soon as I reset it to WP subscriber defaults, with relevant S2 level appends, everything worked as I’d hope it would… except the blog number allocation doesn’t appear to have any intelligence.

I can have a logged out user get redirect for /microsites/
and have a L0 have access to /microsites/ but not /microsites/create/
and have a L1 (who hasn’t created their own blog) have access to /microsites/create/

BUT

for an S2 member (who has exceeded their membership level blog allowance) I get 404, not a redirect to options.

Please will you ask Jason explicitly whether there’s any inbuilt functionality to say what ‘should’ happen when a S2member exceeds their membership level blog allowance and tries to access /microsites/create/. Thank you.

• This reply was modified 4 years, 4 months ago by  David Hunt.

Hi, the 404 is a red herring!
If I create a page and make it child of microsite its url becomes /microsites/create/
If I’m a logged in S2 level 1 I get /microsites/create/ OK with Buddypress embedded create blog fields.

If I then take that user back to subscriber and try to reload the same page I get /microsites/create/ OK but as a blank page ie NO Buddypres create blog fields and no ‘redirection’ to expected S2 options.

This issue has to be incompatibility between the S2 restriction option level 1 = ‘/microsites/create/ or just /create/’
and the Buddypress plug allowing a non S2 level 1 user to get ‘redirected’ back to S2 options.

• This reply was modified 4 years, 4 months ago by  David Hunt.

Sorry Cristian, you caught me messing with ht access.

*this notice applies for ‘not logged in user’

re: Multisite Networking makes a new Registration Form available ( driven by your theme #which is Buddypress ); which we refer to as: /wp-signup.php ( #which is Buddypress /register ). If, and only if, you’re planning to offer Blogs, you MUST use /wp-signup.php, instead of using the Standard Login/Registration Form. In a Multisite installation, we refer to the Standard Login/Registration Form, as: /wp-login.php?action=register.

So no, I’m not using /wp-login.php?action=register

To register a new user I am using Buddypress domain.com/register http://screencast.com/t/p8h04GxiR

Buddypress can only use its own create blog screen here:
To create a new blog I’m using Buddypress domain.com/microsites/create http://screencast.com/t/teeAlsKhR