Grayside.Org - module

Freelinking for Casetracker

Grayside — Fri, 23 Oct 2009 04:31:01 +0000

I use this extensively in my personal issues queue, and it helps. On the inspiration of an issue to colorize the issues in the casetracker views, I’ve fast-tracked this project to provide thoroughly stylizable links to casetracker cases.

Freelinking for Case Tracker uses the latest version of Freelinking to create nice links to casetracker cases, inspired in part on the case linking syntax and styling found on Drupal.Org.

For more about FL3 and it’s course, read my post on it’s current status and future directions.

Terms:

Field Permissions Plus

Grayside — Wed, 23 Sep 2009 20:03:39 +0000

This Drupal module provides a more flexible framework from granting and restricting access to the content of CCK fields.

It provides a simple framework by which you can create multiple modules which cooperate in finding some method of granting access to site users, as opposed to CCK’s core permission scheme in which field access modules are effectively looking for ways to deny access.

Field Permissions Plus makes Field security behave more akin to the rest of the Drupal Permissions world.

Content Permissions Doesn’t Play Nice?!

Well, Content Permissions is fine. But it implements CCK’s hook_field_permissions(), and that function is just looking for an excuse to deny access. By replacing it, it becomes possible to create complex permission schemes with a positive perspective- and a sparse grid of checkboxes.

Different from the Competitors

CCK Private Fields and CCK Field Privacy both operate based on node-by-node approvals, user relationships, and so on. This module provides static permissions.

Why the Name?

This module was partially inspired by #323950 Edit own field permission. In that thread, creating a “Content Permissions Plus” was proposed to solve the problem, because it is too niche a case to integrate into CCK directly. To avoid the confusion of a project specifying Content Permissions, and developer confusion with the CCK’s API, Field Permissions Plus was named. The “plus” is all about the additive nature of the permissions it provides.

{{dp:field_permissions_plus|Field Permissions Plus}}
{{dp:cck|CCK}}

Terms:

field-permissions-plus

Field Permissions Plus: 2.x Already?!

Grayside — Tue, 22 Sep 2009 23:39:48 +0000

Field Permissions Plus has barely been released, but FPP 6.x-2.x-dev is already making progress.

Tonight, a new release will be packaged that separates the View/Edit Own functionality from the core of FPP, creating a new sub-module dubbed Own Field Access. If you decide to test the development version, be sure to enable this module. If you do not uninstall FPP 1.x, all the permissions will still be there with all the same boxes checked.

The biggest difference in 2.x is the new hook- hook_field_access_plus(). This function should be implemented exactly the same as CCK’s hook_field_access, except anything implemented with the _plus version will be deemed an exclusive, instead of inclusive, means of access.

With Field Permissions Plus installed, you can now write two kinds of Field Access modules to create your complex Field Access scheme.

Terms:

Field Permissions Plus: Complex Access Schemes

Grayside — Wed, 09 Sep 2009 22:09:29 +0000

This post refers to Field Permissions Plus 1.x

This Drupal module provides View Own and Edit Own permissions for CCK fields. As a necessary step, Field Permissions Plus supercedes CCK’s Content Permissions module so the View/Edit [all] permissions it provides play nice. With this module, if you give a role the ability to View a field, or to View Own a field, they will be able to see it.

What does View Own (or Edit Own) mean? Well, CCK fields are attached to nodes. If you own the node, you own the fields. This permission enables an author to see (or edit) all the field content associated with his own nodes.

In the future, FPP will be expanded as a framework so other modules can provide additional permissions to expand on how a field might become editable or visible.

{{dp:field_permissions_plus|Field Permissions Plus}}
{{dp:cck|CCK}}

Terms:

Activity Stream for Yelp

Grayside — Tue, 08 Sep 2009 20:11:34 +0000

My first module for Drupal is a simple provider module for Activity Stream. Activity Stream syndicates snippets of content from RSS feeds with the idea of creating a lifestream, like Facebook’s ability to import snippets of your activities in other websites.

Activity Stream for Yelp implements the details necessary to provide users with their Yelp reviews. In the future, their may be configurable options to additionally or alternatively include the review’s of a Drupal user’s business, Yelp social network, or geographic region.

Note that this module currently has no relationship with the Yelp module.

{{dp:activitystream|Activity Stream}}
{{dp:activitystream_yelp|Activity Stream for Yelp}}

Terms:

activitystream-for-yelp