Category Access 0.8.2 Released
I’ve released a new version of the Category Access Wordpress 2 plugin. This plugin allows the blog maintainer to restrict access to posts belonging to particular categories on a user-by-user basis.
New changes:
- Added a workaround for a WordPress bug that was causing the padlock to
appear on static pages when a protected category was selected. (Thanks to
gspark for the bug report.) - Added WordPress 2.3 support (Thanks to James Wurster for the patch.)
- Moved the padlock in the category list to after the name.
- Fixed a bug that was causing problems for people running the German translation. Thanks to Moritz Mueller for bugfix.)
Download it on my code page.
November 18th, 2007 at 3:32 am
I was using Category Access 0.7.2 with WordPress 2.1 which was working perfectly. Today I upgraded to Wordpress 2.3.1 and Category Access 0.8.2. I am having some problems after the upgrade:
1. On the blog index page, I am getting the date, author name and “Posted in X categories” for all the posts that should be hidden from the anonymous user. The post title and content are hidden as they should be.
2. Similarly, on the single post page if I use the URL for it directly, I get the “This entry was posted on …” paragraph as well as all the comments are visible.
3. Of course, that means that redirection to the login page is not working for protected posts in case of anonymous users.
4. The feed shows the title and link for the protected posts despite the fact that the relevant option for Category Access is unchecked.
I am using the default theme for WordPress 2.3. And I have tried disabling the other plugins I am using to no avail.
November 18th, 2007 at 7:29 am
Looking at it, the problem seems to be somewhere in computing the exclusions. On Line 418 of category-access.php, count(exclusions) evaluates to 0 regardless of how many categories are disallowed to the anonymous user.
November 23rd, 2007 at 3:02 pm
Great Plugin! Thank you for creating it, as it is exactly what I have been looking for and wanting for some time now.
I have just encountered a strange thing on one of our servers though . . .
On a test server hosted locally, the Category Access plugin worked exactly as expected – it worked so well that we resolved that it was ready for our production server (remotely hosted and owned by another company).
Once on the remote server (stats listed below) the categories are hidden from all viewers. Once logged in as an administrator, all categories are visible. The issue is that when logged on as an administrator, there is no “Category Access” link on the options page. On the local server it is there and 100% usable – the remote server shows nothing (and yes, the plugin has been enabled).
I thought that I would be “smart” and use the link from the local server and try to append the necessary information to the remote server’s address – that did not work, as the page that was presented with the layout for the template of WordPress, but where one would normally find the “Category Access” information it was blank (it was not a 404, it acted as though there should have been something there but it was not).
The biggest thing that I see as a potential issue as the the remote server’s MySQL version is older than the local server.
Do you have any idea as to what may be causing this issue? I would be more than happy to provide any more information regarding our setup, and explain in greater detail as to what we have setup.
I did try a clean install of WordPress and the “Category Access” on the remote server, and that did not work as well. Any ideas? Thank you.
================
Local Server Stats
================
PHP Version: 5.2.0-8+etch7
MySQL Version: 5.0.32
Apache Version 2.2.3
WordPress Version: 2.3.1
Plugins Enabled:
- Category Access Version: 0.8.2
- Sidebar Login Version: 1.0
================
Remote Server Stats
================
PHP Version: 5.0.4
MySQL Version: 4.1.20
Apache Version 2.0.54
WordPress Version: 2.3.1
Plugins Enabled:
- Category Access Version: 0.8.2
- Sidebar Login Version: 1.0
January 14th, 2008 at 4:58 pm
I’m getting the same problem with setting default access for the anonymous user as described in the comments above. I also notice that the categories I set for anonymous access don’t remain set on the Options page, and that this version of the plugin (but not version 0.6) blocks access to the xmlrpc call to movabletype’s getCategoryList method (it returns no categories).
February 10th, 2008 at 10:00 pm
Thanks for the great plug-in! I have it installed and working with just a few issues. I can still see the post titles, dates, and categories, but not the content when restricting the user to specific categories. In other word, the restricted user can see all posts sans content for all categories. Also, comments can be left on the restricted posts as well.
Any ideas? Is this plug-in still supported? Looks like there’s not much activity on here.
March 9th, 2008 at 2:05 pm
Hi
I have the following problem with this greate plugin:
WP 2.2
Category Access 0.8.2 (German)
SQL-Syntax Error:
Fehler in der SQL-Syntax. Bitte die korrekte Syntax im Handbuch nachschlagen (diese kann f�r verschiedene Server-Versionen unterschiedlich sein) bei ‘ON ( erfahrung_posts.ID = .object_id ) WHERE 0 = 1 OR .term_taxonomy_id = 2 OR .’ in Zeile 1
I think this is an effect of “UTF8″ and wrong in your plugin? The ü in your plugin get an questionmark with black background…
Any ideas?
April 2nd, 2008 at 10:18 pm
Hi, I have tried Category Access 0.8.2 (English) with WP 2.5 and it blocks out the content of the post, but not the existence of the post itself. It just looks like a post with no title and no text. That happens also when I have selected “Hide Entire Post” in the options.
Is this a problem with the new WP version? Do you plan a new release? Do you know anyone who fixed the problem?
Thank you very much for writing this plugin! I can’t believe it’s not part of the standard WP release…
April 2nd, 2008 at 10:23 pm
Hi all,
Yes, the problem with hiding the entire post is one of WP 0.8.2 and later. I’ve been very busy finding a new job recently, but now that it’s done I should have more time to debug this.
David