Pages no longer blocked

I found a support thread about a plugin update from some months ago, and am wondering if that’s my problem. I’ve gone looking for the “Block” “Unblock” custom fields and I don’t find them.

The custom field did change, but the old fields still apply. The only issue is when/if you were changing the status (blocked/unblocked) of a post where the old fields where applied. But there is no issue with that regarding whether the post is actually blocked or not.

Did you change something in your theme?

As I said in my initial message, we changed themes outright. I’m assuming it’s a problem in the new theme. What is strange is that some pages are still blocked, but not all of them (Home page, and the page that is as close as my site comes to a the blog page – where users can post things.) Thanks for any thoughts you might have.

Hi, I might have a similar problem. I want to block SOME pages and ALL posts.

Pages and post are set to Block for default.
“Show excerpts” for pages and posts are off
“Auto excerpt” for both are off

On the individual pages I’ve also set custom fields to “block = 1” and pages still show all content for non-registered. Only Posts are blocked.

But here what’s interesting: on the PAGES (all set to be blocked by default) I put a [–more–] tag on the begining of the content and now it’s blocked for non-registered and a login/ registration appears. But it doesn’t work for me because the only content showing for logged in is a “Continue Reading” link that don’t get anywhere.

I’ve already tried the inverse: set pages to “Don’t Block” and individually check “Block This Page” checkbox and set custom field to “Block = 1” or “Block = true” for each one I wanted to block. No success.

Can’t fin a solution from other entries in this forum.

thanks

I have this same problem as well. I did not change my theme, this happened to me with the Core update. Any ideas what could be causing this? Please help…

Hi, I had the same problem so I investigated what’s going on. I tried many things and the only solution that has finally helped was a complete removal of the WP-Members plugin and re-installation again.

By complete removal I mean: De-activate -> Delete, then I installed the wp-members plugin again and it started working.

There is still an issue with a custom page blocking, it is not reflecting the “blocked” checkbox at a particular page, but the current state of my web is ok for me – i didn’t have more time to dig in deeper.. But maybe it’s good to know for Chad, the developer.

Cheers,

– Max

There is still an issue with a custom page blocking, it is not reflecting the “blocked” checkbox at a particular page, but the current state of my web is ok for me – i didn’t have more time to dig in deeper.

That could be the post meta tag change. You can check by looking at the post editor screen for that particular post and reviewing the custom fields. If custom fields are not displayed in the post editor, go to the upper right of the screen and pull down the “screen options” menu and enable “custom fields”.

If you have a custom field “block” or “unblock”, go ahead and delete it.

Note that in general, the old post meta fields are completely compatible with the more recent versions of the plugin in terms of blocking/unblocking posts.

The only time these old meta fields become an issue is that if you change something from blocked to unblocked (or vice versa).

While this thread seems to have started prior to the 3.1.0 update, but seems to have additional new comments added after that, there is a possibility in 3.1 that could be related.

Let me be clear – the 3.1 issue is specifically based on a misuse/misunderstanding of certain settings and their use. It’s not a flaw/bug/issue with the plugin.

One of the 3.1 updates provides for unblocking the pages that are set as login, registration, and user profile in the main option settings.

Under the old shortcode tag [wp-members], this was always the case – these pages were not blocked. When the new shortcode tag [wpmem_form] was added, this feature was not included with the new tag. This led to a lot of users applying the new shortcodes to blocked pages and then not being able to figure out why certain functions like password reset did not work correctly.

With the old tag, the content was checked to see if it contained the shortcode. But this was an imperfect process for a number of reasons. In 3.1, the process is actually better than the old process – it handles the page by setting rather than checking for the presence of the shortcode.

The issue with that comes when a user has simply pointed the register or login page setting to a blocked page. This setting, if used (as it is optional), is intended to point to a page specific to the purpose.

One final thing to mention is updating from pre 3.x versions. 3.x changed the format of the main options in the settings. While the process is handled of migrating old settings to new, if something goes wrong with that process, you could lose old settings. So it would be a good idea to double check your settings before and after the update.