Hi greyside,
We are following your work since sometime ago and today we finally we found time to test your development. We like to define node-permissions independently from the group permissions as well as create public&private group directories for visitors so your API looks like the best starting point.
We will be back soon with feedback. :-)
Any case, just a silly issue:
$ drush dl og_privacy
There is no *recommended* release for project og_privacy on Drupal 6.x. Ask the maintainer to review http://drupal.org/node/197584 and [ok]
create/recommend a release in order to be compatible with drush and the drupal.org security broadcast system. A recommended development snapshot
release is sufficient. Alternatively, run pm-releases command and explicity pm-download any non-recommended release that might be available.
As is said, it's not important, but will be more comfortable for everybody if you if you flag a your devel snapshoot as recommended... although all this code is still beta.
Thanks for your great work,
Marc
Comments
Comment #1
Grayside commentedHi Marc,
I appreciate your interest in OG Privacy. My next release will be marked as Recommended. I am trying to leave some slight barrier up for folks because the current release has some bad UI bugs, and a critical security flaw when used with Spaces OG.
Once I have a few hours to finish wrangling the Spaces OG issue, I will create a new release and make it recommended.
Comment #2
Grayside commentedRenaming. Drush integration does have a potential role to play, but it's a very different sort of issue ;)