For distributions, it might be nice to make sure that the word "Drupal" is not hard-coded to appear in any user-facing text (ex: variable_get('site_name', 'Drupal'), code (ex. drupal.js), or other output (ex: X-Mailer: Drupal), replaced instead with the name of the profile that's installed.

This is going to be way too much work for D5 and is remains to be seen as to whether or not it represents a serious enough problem for distribution authors to go into rolling a huge patch for this. However, I'm creating a postponed talk for it just in case.

CommentFileSizeAuthor
#2 en-US.po72.17 KBRobRoy

Comments

michaelfavia’s picture

michaelfavia commented
Version: 7.x-dev » 6.x-dev
Status: Active » Postponed

To echo my comment on issue #97941: String freeze: make site_name's default value consistent.

The details of an implementations shouldnt be shown to any end user (read: visitor) in my opinion. Genericizing it to the degree possible is a feature for future distributions and private label users who dont want or need it known that drupal is running under the hood. The people who need to know it is running drupal will know it is running drupal.

We use clean urls to provide memorable and implementation agnostic addresses and i think this is a natural extension of "drupal as a tool not a destination". As much as I like to see it everywhere I just don't see a valid reason to be flashing "Drupal" around on everyones sites.

RobRoy’s picture

RobRoy commented
StatusFileSize
new en-US.po72.17 KB

Agreed, for a lot of projects I work on they want a white label solution. I have a recipe like this which I keep in SVN.

  1. I've been using locale JUST to get rid of Drupal references which is a big performance hit so I'm all for generalizing! White label .po file attached, it's a pretty straight find and replace from 4.7 so it doesn't really make tons of sense, but it might give us a place to start.
  2. I renamed drupal.* files to common.* and removed all Drupal images from misc/
  3. Removed themes that show a screenshot saying Drupal in admin > themes
naudefj’s picture

naudefj commented

I need this as well. With Drupal 4.7 one could use code a phptemplate_stylesheet_import() function in template.php to rename drupal.css to something else:

<?php
 function phptemplate_stylesheet_import($stylesheet, $media = 'all') {
   if ( strpos($stylesheet, 'misc/drupal.css') === false ) {
     return theme_stylesheet_import($stylesheet, $media);
   } else {
     return theme_stylesheet_import(base_path() . 'misc/site.css', $media);
   }
 }
?>

However, I could find nothing in 5.x to rename drupal.js to something else.

lilou’s picture

lilou commented
Version: 6.x-dev » 7.x-dev
webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Postponed » Active

No reason for this to be postponed anymore. We're in code thaw now. :)

Anonymous’s picture

Anonymous (not verified) commented

subscribe

lilou’s picture

lilou commented

see also : #182991: Standardize on "internal path" instead of "Drupal path" or "system path"

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Version: 6.x-dev » 8.x-dev
Status: Postponed » Active

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dpi’s picture

dpi
Location Perth, Australia
commented
Title: Remove the word 'Drupal' from all user-facing stuff » Remove the word 'Drupal' from interface
Version: 8.6.x-dev » 8.8.x-dev
Component: base system » user interface text
Category: Task » Feature request
Issue summary: View changes

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

quietone’s picture

quietone commented
Status: Active » Closed (duplicate)
Related issues: +#2144861: [meta] Replace Drupal in UI text with the name of the distribution

There is a more recent issue for this, #2144861: [meta] Replace Drupal in UI text with the name of the distribution, which is a Meta with child issues that have patches. Because there is more work on that issue closing this as a duplicate.