Drupaluser is aproject which can be used for dummy projects.It is under active development.
This module allows you to configure a menu management, publishing for the client or the publisher.
With this menu you can select the pages or page types that they can view or edit in a dashboard are custom shaped menu accesible by the customer no matter the place where it is located.
Create and configuring easily the hierarchy Subdirectory multi-site for your Drupal multi site from one installation and a single shared database . This module allows you to add new subdomains directories or management of subdomains directories without changing/adding any file configuration (.htaccess, sites.php, Alias in Apache config file, ...)
Ex: example.com/site-1, example.com/site-2
- Live Demo Site
Username : demo
Do not forget to read the Master File README.txt for more information related to the installation.
Supplies 2 new blocks for the Profile Complete Percent module:
Profile Complete Percentage - All Profiles
Supplies percentage complete for all profiles put together.
Profile Complete - All Profiles with Names
Supplies a block with a list of profile type names and 'complete' class if profile type is completed by user.
The User Disk Quota module allows to limit user disk space usage per single user or per user's role.
How the module works
Each user could be limited on the total size of uploadable files. The limit could also be set per user role.
The disk space limit, by design, works only for file uploaded through Drupal form API. FTP uploaded files could not be counted on disk quota total size.
User Disk Quota integrates with the following modules:
There are many ways you can actively contribute to this module:
- Translate module's strings in your language using localize.drupal.org
- Help the module mantainer to improve user experience by suggesting better and clearer english tenses to be used on module's administration pages
- Test and give feedbacks to issues needing user reviews
Fast Admin creates automatic administration Views for each content type, one view per content type.
There are plans to implement:
- Integration with other modules (draggable views, votingapi...).
- Automatic creation of Views for any Entity (taxonomy, user...).
- General configurable options.