features

I'm building a website that consist of a main website and three office locations/branches websites. The main website pulls content from all three locations.

Location websites must have a 'home page' with a unique url, as well as the main website ofcourse. Each location must have an allocated admin role that can manage that location content only.

GoingOn (http://www.goingon.com/) is actively seeking Drupal developers who can create high quality modules for our platform. We are building upon a Spaces, Features and Organic Groups system, so much of the work we will contract out will be building og_spaces compatible features and any modules necessary to drive the feature. We're building a social e-learning platform on Drupal where many of the features will be social, collaboration and education focused.

Hia, sorry if this is a stupid question, but I'm struggling to build (OG) features of modules that does not use Views, as I do not know how to filter for Space without Views.. With Views you select the spaces filter, and set for instance "show nothing" when node is not in space.

But, what if the feature I wish to build does not use Views? Am I out of luck?

I was playing around with integrating Atrium and the Features Server feature and thought I would share my basic process. This is in no way perfect but it's a start. Please add on other useful pieces of information.

Thought that I would start a list of the various modules and threads for creating a Drupal-based family tree.

TNGintegrate http://drupal.org/project/tngintegrate
Family Tree 2 http://drupal.org/project/family
Genmod http://drupal.org/project/genmod

http://drupal.org/node/395586
http://drupal.org/node/25589

Was also wondering if others have genealogies 'working' on their sites whether they could pack them up as 'features' [see this video http://www.developmentseed.org/blog/2009/may/29/making-and-using-feature... http://drupal.org/project/features ].

Hi all,

I’m planning to contribute a module which will offer nodes import export capabilities for features, let me know what you think about it, if it makes sense to have something like this etc...

Here its description:

Features Content

The module enables Features to export/import nodes objects (along with their files, menu items and CCK fields) in a feature package. For each feature it is possible to decide which node to export (based on its NID, type, etc...) and if to keep its NID or to recreate it from scratch to the next feature import/update. For the moment authorship export is not supported: all the imported nodes will inherit a common user UID (configurable) if their own is not present in the system.

Just watched this screencast http://www.developmentseed.org/blog/2009/may/29/making-and-using-feature... and am really amazed by this.

Is there any place where features (not the module) can be downloaded from? To be able try this out with something like that Discography feature would be great.

I'd like to brainstorm some of the typical features that would make sense to include on an "out of the box" lodge web site:

• WYSIWYG editor
• IMCE
• Calendar
• News page
• Officer profiles
• Photo galleries
• Private OG for committees and other internal discussion groups
• Access control for members-only content / downloads
• Roles for members, officers, content editors
• Contact form
• Path/Pathauto
• Stock top-level pages & primary links ("About/History/FAQ/Contact")

I'm not sure how many other people might have this problem, but I was wondering if there was some way to make a post sticky for just a particular group?

Use case: I am organizing a regional event that I would like to cross post to other nearby groups who may be interested, and make featured/sticky on the local groups homepage. However, if the post is marked sticky then it becomes sticky for all groups and seems rude, at the very least, if not abuse to impose the importance of one group on the other groups.

Recently launched Drupal site HollywoodChicago.com is looking for a skilled, experienced, talented and reliable Drupal developer to make ongoing feature improvements and site updates. The site exists in a LAMP environment. Some coding requests to the overall site will be required, but in general, we are seeking a Drupal developer to make upgrades on an as-needed basis.