I am working on a departmental website within a big university and want to add different types of functionality for different users depending on their roles.
There are 3 main types of users:
Publicly listed
Alumni (listed but based on different fields and using a custom template file)
Others (users on site but not listed)
Right now we are using Content Profiles for the publicly listed users and list the content in the core profile tables for the alumni.
The problem is: If I'm faculty I still see all the fields for alumni (although it is in its own tab) and if I am alumni I see all the fields for faculty.
Question: What I would like to do is provide them different views of editing "My Account" based on their roles. So I wonder, would it be possible to do this with organic groups or is this something that needs custom PHP coding?
Thanks for the help
If you're asking about limiting fields, then it has nothing to do with OG.
I think you're looking for the conditional fields module.
This way you can set a node as 'alumni' or 'faculty', and depending on it show different fields.
Related
I am working on a site that is built around articles and videos. Additionally, members sign-up and create a profile. Within that profile, there are "interests" that they can select in addition to some categories we place the user in based on other behavior.
My issue is that I am trying to create logic that will display articles and videos based upon three variables. The variables are below. What is the simplest way to do this?
1) For members who have selected and "interest" I want to serve articles that have been tagged in the system as associated with that "interest" with the articles that have been most recently posted shown first.
2) For members who I don't have an interest for, but I have placed in a bucket based on behavior I want to serve articles that have been tagged in the system associated with that "bucket" with the articles that have been most recently posted shown first.
3) If I don't have an "interest" or a "bucket" I just want articles to be served by most recently posted.
Thanks for your help.
I would recommend using the Profile module. This will allow you to customize the User Account Creation form and add in custom form fields [suchas term references]. This also will allow you to create relationships between each user and specific content. [Show all content of type X, which shares interests with the current user ID.]
https://www.drupal.org/project/profile2
I've used it and it's pretty awesome.
I want to make site that displays form, and makes user capable to input certain parameters in it. For example, real estate site. Let say I have these fields among others: location, price, size. If user choose to see houses under 100 000$, Drupal has to back node teasers (fields) for houses only under that price.
Now, I wonder how to make Views module start searching when user click submit button, and how to make conditions under which Views search, dynamically dependent of parameters users put into form.
Do I need some additional modules beside Views and Webform modules? Or maybe, I don't need them? Maybe I have to write some php/mysql script that do searching and fetching, but, naturally, I think Views module is build for that kind of circumstances. Thanks in advance!
1) There is an option in Views when you create the exposed filters: "Remember the last selection". This caches the user selection for each Views and when user visits the Views again he will see the previous filters enabled.
2) For better UX you can use Better_Exposed_Filters and Views_Saved_Searches modules. With the first one you have much more options for exposed filters (eg expose as checkboxes) and with the last one users can save their searches and use them later (like bookmarking a url path).
PS. I don't think using the Webform module with views will be useful in order to create personal saved searches. Instead, Views Saved Searches is what you are looking for.
This is my first experience building a site with Drupal and am still learning about all I can do with it.
I am trying to figure out a way to configure sort of a second level of user roles consisting of roles defined with permissions. The users of the site will be group members with various titles, for example: Manager, secretary, web admin, etc. Each of these titles will have responsibilities within the site. The users tied to these titles change though and I would like re-configuring this in the site to be as easy as possible (will be for someone unfamiliar with Drupal).
I am thinking configure permissions into roles such as content editor, file uploader, etc based around the responsibilities each title will have. Then I would need an additional role editing page (probably custom) that would show a similar table to permissions/roles but would be with roles/titles where the site admin could easily take a person with say secretary title and easily provide them the ability to edit dates, or upload files, etc.
This would make it easy in that the site admin would only be presented with the titles and the abilities defined for site usage, and not have to comb through the entire list of permissions.
The second issue with this would be then how do I assign titles to users. Ideally it would be the same as assigning roles within a users account page.
Any suggestions/ideas?? Thanks in advance!
The more Drupal-ish way to handle this is to just make your individual roles ("content editor", "file uploader") into the roles and assign multiple roles per user. So instead of there for example being a "Manager" title which gets the "content editor" and "file uploader" roles, you would just assign those two roles to users directly and avoid the notion of the "manager" title altogether.
The other obvious option is to just make your titles the roles, meaning that the "manager" role gets all the permissions that would otherwise be given to "content editor" and "file uploader".
Both of those methods avoid the notion of two levels of roles and since that's not really how Drupal is supposed to work, it will save you lots of pain to go this route.
I am new to Drupal. I am working with a preexisting website that has a couple dozen staff bloggers. Some of the bloggers need to have all of their posts migrated out to a database (the CMS they will be imported to is not yet known).
I have looked into a few modules for backups, but they don't seem to have the ability to choose what exactly is exported.
If anyone could give me some advice or direct me to an appropriate module, that would be fantastic!
You can do it easily with Views and Views Data Export modules.
However, you will need to learn a little about Views before making use of the Data Export module. You can follow some quick tutorials. You will not need any coding skills but concentrate on Views UI , Filters and Arguments.
Make a View on node as primary content, and add a filter (or an argument if you want to take the user ID from URL) for User: UID and add fields you want to get exposed as Fields. Then, in the style settings, choose "Data Export". Create a page display and give it a path.
You can also make the form advanced with exposed filters.
I have been searching all morning and have yet to come across the solution for my problem..
problem is:
I have successfully created a CCK content type using the content taxonomy module (which allows me to use a vocabulary as the content). the user is asked to select his/her preferred cultures. so in simple terms form holding a series of checkboxes which the user merely selects their preferred cultures.
problem comes when I wish to display the selected cultures by that user for them to then sort into their top 5 cultures.
the sorting bit I can do using draggable views. however actually displaying the users selected cultures is something im finding difficult.
sorry for my novice of a question.. but its been one of those days.
You should use relationships.
HOWTO: Views 2 Relationships: http://drewish.com/node/127
User Relationships module: http://drupal.org/project/user_relationships
http://www.drupalforusers.com/content/using-views-2-relationships
Using Drupal's Views Relationships: http://www.drupalove.com/drupal-video/using-drupals-views-relationships
Also you may need this patch: http://drupal.org/node/241078.
Or a module that allows to make backrelationships but it is private.