Anyone know a Module that can create additional fields for a user in Drupal 7 ?
Example: First name , Last Name , Telephone Number.
And then To Display those user fields in a list page using views ( example Telephone List)
I have tried the "Profile 2" Module for Drupal 7, it looks great , all the fields you add gets a place on its own in the users profile. But really thats all I can do with it , as far as I know. I cant use those fields for anything in views. They are not there. And I find no dockumentation for that module (Profile 2 )
Likely a basic question and I apologize, but i cannot find information for a simple way to change how my image fields are laid out on a in a content type in Drupal 7? I want to be able to simply insert an image or a series of images in a content type and then control the final look of the node (e.g. lay it out with one field floating right justified and have another field which allows multiple images laid out horizontally with padding between under the body, etc.).
I installed Drupal on a GoDaddy subdirectory as a test site, got it working, and then created a new hosting account under a new domain to deploy the main site. I'm confused now, though, because I never had any problems with installing Drupal on GoDaddy until now. I didn't really have a clean install - I got some permissions errors after the main configure setup, and nothing seems to be going well. I'm getting permissions issues on everything... what am I doing wrong? I can create nodes, but I can't add modules, themes, or run cron without getting red text each time. I followed the instructions in the installer guide to the letter.
Warning: opendir(/tmp/update-cache) [function.opendir]: failed to open dir: Permission denied in DrupalLocalStreamWrapper->dir_opendir() (line 700 of /home/content/20/7361820/html/includes/stream_wrappers.inc).
Warning: opendir(temporary://update-cache) [function.opendir]: failed to open dir: "DrupalTemporaryStreamWrapper::dir_opendir" call failed in file_scan_directory() (line 1975 of /home/content/20/7361820/html/includes/file.inc).
Warning: opendir(/tmp/update-extraction) [function.opendir]: failed to open dir: Permission denied in DrupalLocalStreamWrapper->dir_opendir() (line 700 of /home/content/20/7361820/html/includes/stream_wrappers.inc).
I work on a Drupal site that was built by a previous developer.
There is currently a Page View that is a long list of all 'Blog' node types (teasers) for the site. The path for this page is '/blog'. Blogs can be tagged with terms from two different vocabularies.
In the view, there are two arguments that have been set up. These are term ids for the two different collections of taxonomy terms.
So they have the path of '/blog//' to filter on both terms
or it can also be '/blog//all' to just filter by of the terms.
Hi,
I have been trying to define default behaviour regarding the Menu parent item and url alias for each content type since the users creating the content types shouldn't have permissions to set these settings.
So imagine I have a content type called Type1, with a link for it on the main menu. Everytime I create new content of type1 i would like it's menu parent item to be Type1:
I am setting up a "multi-site" drupal 7 site. In my case that means:
- A user must be able to create his own domain: http://mydomain.example.com . Even multiple domains per user should be possible.
- A user must be able to add content (picture albums, blog posts, other content types, ...) to his own domain
- A user must be able to select a theme for his domain
- A user must be able to select a language for his domain
- A user must be able to set permissions for his own domain
- All menu's are equal for all domains to begin with. Maybe in the future, a user might be able to add his own elements to menu's
I am not sure which modules to use to achieve this. Here are a few ideas:
- Consider each domain as a separate site, each with a separate database. This doesn't seem the right way to go. Updating alone seems like a hell
- Domain access module http://drupal.org/project/domain . This seems like the best bet. Although not the easiest module to use if I browse through the txt (!) help file. Also, the typical usecase for this module seems to be setting up 3 or 4 different sites with one shared database, not dynamically creating new domains.
- Organic groups http://drupal.org/project/og . This seems easier to set up than the Domain Access module but I don't think it fits my needs perfectly. I think it is harder to separate different domains completely with og.