Hi, there, I haven't yet designed my site for Drupal users - right now it gives all content to everyone (anonymous users). Is there a way to have multiple level subscription products (each that cost differently and have additional conent)? If so, how do you do this and setup your content so that only "Level 1" users get a certain amount of content, "Level 2" users get additional content, and so on? Sorry if this is obvious, and have a good day, all - Paul
Hi, Protection should be done in Drupal itself. You should assign correct permissions for user's roles Then assign each role to amember product in aMember CP -> Manage products -> Edit Product -> Drupal access
I use a contributed module called "TAC_Lite" to restrict content permissions to selected roles. Then, all you have to do is assign Drupal roles to your aMember products and you're all set.
I've heard a lot of good things about Drupal... is it a good platform vs, say, WordPress for a media-heavy membership site? Is the bridge to aMember as Alex described it above a good way to go?
I've used Drupal for several websites, and I like it. With every new version, it gets easier and easier for newbies to use, which was the only negative thing about it when I first started. I haven't used WordPress, so I can't offer a direct side-by-side comparison of the two. However, I've looked into WordPress and it seems very limited to me compared to Drupal. I've only found 2 downsides in the integration between Drupal and aMember. The first is when trying to show aMember data inside the Drupal members area. I use an iframe to include the member.php page into a Drupal page, but I'd like a better integration. The second is when aMember is protecting downloadable content via NewRewrite and a member comes back to the site a day or so later. Drupal sees the member as still logged in, but aMember doesn't, which means there is some juggling to access downloads again, since a simple right-click doesn't seem to work with NewRewrite.
I'm sure there's a solution to it somehow, although I haven't looked into it enough to find it. I think it is possible to force a Drupal logout each time, although my preference would be to allow persistent logins.