[Blue Owl]

I reproduced the issue on a fresh install with just eMember, Smart Blocks and the 2010 theme, and submitted the user info to you. Thanks!

[Blue Owl]

Thanks. I’m not using any category protection.

I’d just love to stop the content of my Smart Block widgets being protected on fully protected Pages with no section protection on them.

[Blue Owl]

Ok, I’ve double-checked and none of the check boxes are ticked.

See [https://img.skitch.com/20120309-k8h4du45tx9yqeesq5myfw3p8q.jpg]

Isn’t that how it should be?

[Blue Owl]

Hi. Okay, I’m fine with not mixing the two types of protection.

The first troubleshooting I did was to check I haven’t protected the custom post type, but the custom post type doesn’t show up as an option in eMember settings. There is the option to protect the Smart Block on the Add/Edit Smart Block panel, but they’re all unprotected.

So, I’m assuming eMember isn’t recognising that Smart Blocks are not page content. And that’s as far as I’ve gotten.

[Blue Owl]

Here’s a url where you can still see the Smart Block problem I’m having:

[http://theleakybathtub.com/products/the-leaky-bathtub/leaky-bathtub-premium-download/]

[Blue Owl]

I’ve made a change to the url I mentioned above.

Originally I had the boxes checked for multiple membership levels for this page, in the Edit Page panel. I also have Section Protection shortcodes, so members from different levels (who had access) would see different sections.

Isn’t it possible to have both types of protection (page and section) for the same page?

[Blue Owl]

Just wanted to post an update on how I hid the membership level field in the registration form, since it seems there were significant code changes in the past year.

In eMember_registration_utils.php comment out this in lines 605-608

<!– <tr>

<td><label for=”wp_emember_member_level” class=”eMember_label”> <?php echo EMEMBER_MEMBERSHIP_LEVEL;?>: </label></td>

<td><input type=”text” id=”wp_emember_member_level” name=”wp_emember_member_level” size=”20″ value=”<?php echo $_POST;?>” class=”validate[required] eMember_text_input” readonly /></td>

</tr> –>

[Blue Owl]

Just wanted to post an update on how I got this done, since it seems there were significant code changes in the past year.

In eMember_registration_utils.php comment out this in lines 605-608

<!– <tr>

<td><label for=”wp_emember_member_level” class=”eMember_label”> <?php echo EMEMBER_MEMBERSHIP_LEVEL;?>: </label></td>

<td><input type=”text” id=”wp_emember_member_level” name=”wp_emember_member_level” size=”20″ value=”<?php echo $_POST;?>” class=”validate[required] eMember_text_input” readonly /></td>

</tr> –>

[Blue Owl]

Any update on this?

[Blue Owl]

(double post)

[Blue Owl]

Thanks very much! Just to clarify – if a member does not renew their membership when it runs out, they’ll have gotten one reminder notice beforehand, and one ‘Your membership has expired’ message afterwards.

But, is it correct that the site owner does NOT get notified about expired memberships?

If so, and if it’s still the case that you can’t automatically unsubscribe someone on an AWeber list when their eMember membership expires – how would you be able to know that it’s time to manually remove someone from the AWeber list?

[Blue Owl]

Did Aweber introduce the HTTP POST method yet?

[Blue Owl]

Hi,

Has this option been added since last year?

Thanks!

[Blue Owl]

Sure. I get that.

I would like to skip the message that says “Please Login to view this Content…” and rather than that, go directly to a page with the login form on it.

So, eMember would redirect the visitor straight to the login form when they click on a link to a protected page, rather than arriving at the protected page first and then needing to click a link to go to the page with the login form on it.

Right now it’s this process:

Click a link to protected page > Arrive at protected page > Get ‘Please Login’ message > Click login link > Fill out and submit login form > Return to protected page

I would like to remove a couple of steps so it goes like this:

Click a link to protected page > Arrive at login form > Fill out and submit login form > Proceed onto protected page

Does that make sense?

[Blue Owl]

Sure. I get that.

I would like to skip the message that says “Please Login to view this Content…” and rather than that, go directly to a page with the login form on it.

So, eMember would redirect the visitor straight to the login form when they click on a link to a protected page, rather than arriving at the protected page first and then needing to click a link to go to the page with the login form on it.

Right now it’s this process:

Click a link to protected page > Arrive at protected page > Get ‘Please Login’ message > Click login link > Fill out and submit login form > Return to protected page

I would like to remove a couple of steps so it goes like this:

Click a link to protected page > Arrive at login form > Fill out and submit login form > Proceed onto protected page

Does that make sense?

[Author]

Posts