A group for talking about Drupal distribution profile development groups.
Created as an informal response to Dries' blog entry about potential pitfalls in creating Drupal distribution installation profiles, the intent of this group is to provide a forum for discussing the topic on a very broad scope in the interest of promoting collaboration, cooperation and communication among developers.
This group is a good place to: announce new projects and the goals behind them, identify common goals and best practices for distribution profiles as a whole, explore options for collaboration and consolidation where possible, and collaborate with developers working on unrelated installation profiles in order to present their sum as a consistent experience to the end user.
Should maintainers be able to place files in arbitrary locations in the installation profile's directory tree?
Should install profile maintainers have control over where contributed projects are included in the packaged tarball?
What should the suffix be for the files that installation profile maintainers use to define the packaging?
Should the version strings for installation profiles include the exact version of core they contain?
Hello, there is a funded contract available to build an Drupal profile for an Arts community in Los Angeles.
· Raise awareness by informing the general public about the importance of art and arts education in society
· Network communities (regional as well as by discipline or particular issue, i.e. public funding, municipal support etc)
· Provide an advocacy tool kit and best practices for arts and arts ed advocacy in the region
· Activate/mobilize individuals and communities to participate in this regional advocacy movement.
Having worked recently on install profiles with the Filmforge project and the install_profile_wizard module, I am becoming less and less confident in their effectiveness. There are three key issues that need to be adressed IMO.
First, install profiles are currently prone to failure when you have different versions of modules. Install profiles should be able to list the version (update) number of each module currently installed, in order to be able to make the necessary updates during the install.Read more
While the length of time I have procrastinated in posting this is shameful, although I lurk regularly still, I have not so much as created a sandbox install in the last couple of months as a result of personal obligations.
I can't say how gratifying it's been that this group didn't die immediately from lack of interest but has actually flourished and achieved it's goals.
But I don't actually post here, let alone do anything management like, so I really need to ask if anyone wants to assume management, just so that one of you has access to the added functionality?Read more
This release features both security and maintenance upgrades.
For new users, this is the best version to download and install. The download tarball contains a directory named "Instructions" that contains some instructions on getting started. For additional help, and/or to get involved with the DrupalEd community, submit issues to the issue queue or join the DrupalEd group.Read more
I am wondering what success other people are having with this capability? In theory it is great, but in practice not so much. At least not for me...
In my setup the menuing of System1 is not maintained in System2 - there isn't a menu.
I've been comparing the tables of the two systems and combing through the generated .profile but nothing is jumping out at me.
I'm wondering if I should abandon use of the Wizard and just leverage the functions in crud.inc ?
I guess this group is here to talk about install profile projects so here is a post about mine.
I am working on creating an install profile for the Industrial Workers of the World, which is a union I am a member of. Currently the main site there runs drupal but most of the branch sites are hand-coded HTML with various degrees of skill, design etc. I think the Starbucks Worker's Union probably has the nicest site in the union.Read more
So - we have all these all great profile ideas, and someone's gonna need to do them... most of them already have site recipes or something of that sort, we just need someone to do them. I'll start with a list, and if you want to do a profile, add your name.
I'm trying to think about whether or not this should be a profile:
- Fivestar/votingAPI as CCK fields
- other random utility modules
- Locations/businesses: nodes
- Reviews: nodes as node reference
- blog posts
- that's it!
So, I write here to gain input and see what other folks think about this as a profile.
Get release 5.2-1 here.
From the upgrade notes included in the release:
This upgrade is in response to the CCK security announcement.
While this security upgrade only affects a specific use of CCK that is not present in the DrupalEd configuration, anyone running DrupalEd is strongly advised to upgrade. A healthy dose of paranoia regarding security concerns can save you hours of time/emotional distress.Read more
Hello, CivicSpace has released a set of APIs for creating hosted Drupal and CiviCRM profiles.
Hosted profiles are different than Drupal distributions in 3 key ways:
1) Hosted profiles can be updated in production.
2) Hosted profiles can be changed from one profile to another for example. e.g. Basic Drupal to Drupal for Education
3) Hosted profiles can can add, remove modules, and move files. This should not be done with Drupal code as it would be insecure.
I just tried out Drupal's installation profile feature for the first time this week and think it has a lot of potential. Using the Install Profile API and Profile Wizard, I was able to create a customized .profile in just a few hours. In the process, the following ideas occurred to me for ways that the installation profile system could be improved further:Read more
All users of DrupalEd should should know about a security upgrade to Drupal core. As this is a security upgrade, people with sites in production are advised to upgrade immediately.
The announcement, with upgrade directions, can be read here.
The new version of DrupalEd with all security patches applied can be downloaded here.
I've started writing up a handbook on lessons learnt when setting up a more centrally-administered site.
Drupal is set up to maintain community-based sites out of the box, with comments, blogs, forums, and multiple users and roles integrated as part of core.
However it's also a very strong platform for centralized, traditional Content Management and a full web development platform, from a brochureware 'about us' site presence to full ecommerce site or knowlegebase.