Remove "Powered by Drupal, an open source content management system"

By olydna on 10 Nov 2008 at 02:18 UTC

How can I remove "Powered by Drupal, an open source content management system"?

Thank you!

Comments

=-=

VM commented 10 November 2008 at 02:19

administer -> blocks and turn the block off that is in the footer.

Or Edit page.tpl.php and

itqn2004 commented 10 November 2008 at 09:25

Or Edit page.tpl.php and remove it.

http://jobs68.com
Build Drupal website please contact me itqn2004@gmail.com
TanTran

Edit the tpl?

add1sun commented 10 November 2008 at 12:13

Er, since it is a block, you'd have to remove the entire footer region in the tpl, which in most cases is less than desirable. Simply disabling the block is the way to remove it.

Lullabot loves you
--------------------------------------
Join us at Do It With Drupal!
A large scale, curated education event
December 10-12, New Orleans

Drupalize.Me, The best Drupal training, available all the time, anywhere!

All the Software name pointers are carte blanche for Hackers

domineaux commented 10 November 2008 at 14:54

Helping out the hackers...

Click on the browser tool bar View and then Source. Run a quick search and you'll see Drupal all over the page. I don't where you go on a Drupal site, there it is.

Hackers aren't seeking out sites like many of us invision. Most hackers never even pay attention to sites until they get word of a vulnerability in an internet software.

All you do is type vulnerable, vulnerability, security patch, etc. into Google and Voila! There you have all kinds of ways to find vulnerable software.

Then you Google the name of the software that has the vulnerability and Voila! There you have all kinds of ways to find the installations of the vulnerable software.

Hackers don't have to work at it too hard to have their perverted fun. All their work is done for them. That is why you'll find the hacks have a definite pattern of abuse.

I realized this years ago when I worked with Xoops. My gosh every module, every page had Xoops scattered all in the coding. The hackers would eat you alive.

Now that things are advanced, we still have the same thing.

I know Drupal, Joomla, Xoops want to keep a handle on the product. I'm just wondering if there isn't a better way to do it that isn't sooooo obvious and BOT trackable.

The best way to protect your sites, is to install security patches immediately on all your sites. The hackers aren't lying in wait, they're taking their time and they still nail thousands of softwares that actually have security patches released. The devs just haven't applied the patches.

I just had a bunch of sites hacked on a host server.

Security releases for the vulnerabilities that were exploited were issued eons ago. Remind the support people hosting your sites to install security patches. If you get word of vulnerabilities... telll them.

Often when your sites are hacked you will probably have to do some work yourself, not just the server support people. If you have a bunch of sites up... you'll get to work alot.

=-=

VM commented 10 November 2008 at 15:40

not at all sure what this rant has to do with the topic. The user simply wanted to remove a block and mentioned nothing at all about hackers.

I focused on his wanting to

domineaux commented 10 November 2008 at 16:22

I focused on his wanting to remove the Drupal...for whatever reason he mentioned.

I just got over 10 domains hacked on one server, and my day was pretty well screwed.

Be patient with me, I mean well... somedays I need to get into the coffee earlier.

opening "Powered by Drupal" in new window

dewcansam commented 20 September 2009 at 18:39

Hope this helps anyone.

I did not want to remove the "Powered by Drupal" link but, at the same time i did not want it to replace my site. So,,,,

issue: need to get "Powered by Drupal" to open up in new window / tab

solution: have to add attributes to the link

open up ./modules/system/system.module in your editor
very bottom lines are the ones you want to mess with (mine it was 1935L)
+added $attrib = array("target"=>"_blank");
*edit change return l($image, 'http://drupal.org', array('html' => TRUE, ...... to return l($image, 'http://drupal.org', array('attributes'=>$attrib, 'html' => TRUE .....

and there you have it drupal.org opening in new window ;)

=-=

VM commented 21 September 2009 at 04:13

hacking drupal core for this is silly.

It's far better to just create a new block and add the proper HTML to it to get it to open in a new window.

Well i disagree with the term

dewcansam commented 5 March 2010 at 12:59

Well i disagree with the term "silly". But trying to understand where you are coming from let me address it this way.
I love drupal and love all the great work that they have put into it however, to take over my site by having the drupal logo point to the drupal home page and removing my site is just as "silly". In reality Drupal should consider that customers sites are there for a reason and SHOULD greatly consider that the Drupal logo should open in a new window.
Hacking the drupal core should NOT be encouraged by users who are not familiar with PHP and any new updates will overwrite the code to begin with. Meaning that you will have to add the line back in. In that sense you're right it is "silly".
However, changing that one line took less than 5 seconds and has no overhead that is required with creating a new block and all the calls to the DB. Also, lets consider that you have 20 themes installed that means you will have to create 20 blocks for all the themes and then click and move / drag them to the correct display location could take hours on end.
Then let's look at the overhead involved in the DB queries if you were to have 100 simultaneous user connections that is going to way overtax my little system with un-needed queries.
However, i have come up with a better way. Take at a look at my site here http://dcs777.homeip.net/?q=node/163 for a javascript that looks for all external links and adds the target attribute to open in a new window. Why mess with blocks or code when you can have the client do all the work ??

=-=

VM commented 5 March 2010 at 18:37

actually you could create a single block in a custom module which would allow it to work with all themes, though it would have to be enabled on all themes. This too would likely create "overheard". Thankfully, not the way I'd build sites with multiple themes able to be used.

There is more than one way to skin a drupal cat. If you are have the skillset and the understanding of what hacking core means in the long run withj reference to bottom lines, man hours and inevitably costs, thats great. Many don't though and when they hack core or hire someone that hacks core and those users update their install only to lose stuff it puts a burden on many.

So let's see, hack core and have to make those changes every time I update and use more human resources or turn it over to a new block or custom module and reduce the human resources over the long run. In that respect, I still view hacking core for this type of task .... silly.

The javascript idea is interesting and is similar to the already existing extlink.module which allows one to set all external links to open in a new window. But, yes this too will use a bit more overhead on the server but save man hours over the long run.

My cost benefit analysis tells me that developers time is expensive and in having to rehack core with each update is far more expensive than using a new block, a custom module or an already contributed module. Turning things over to the client isn't always appropriate either. What about users of your site that have .js turned off in their browsers? how does a javascript method work for them?

Also of note, you discuss overhead but the downloading of another js library can be seen as overhead as well. Is the method you propose using jquery? I'm not js literate enough to tell the difference. If it isn't using the jquery library which already ships with drupal are you not also adding unnecessary overhead?

I was interested in the

gurlinthewurld commented 7 October 2010 at 23:47

I was interested in the original issue of removing the "powered by ... " and found the whole thread relevant, interesting, and a little scary. As a newbie, when I installed Drupal and asked around if I could create a www directory to avoid dealing with command line (I'm not a sys admin person), and to be able to upload files via ftp, I was told this could be dangerous. But how do most of you out there update to your site? Is everyone using the command line?

Other than keeping really complex, frequently changed passwords, how does someone like myself take precautions to web site security issues?

Once again, tia, gg. Very much obliged...

the logo

mcfilms commented 10 October 2010 at 00:21

We've kind of gotten off track from the original question. VM's post was so susinct that it might have gotten missed. To turn off the Powered by Drupal artwork and link:

Visit administer -> blocks and turn the block off that is in the footer.

It's that easy.

In regards to the next question, I don't find it necessary to use the command line at all with Drupal. I'm a proud Dreamweaver and FTP user. Computers were supposed to be made to work for us, not the other way around. I hear about the great things people do with GIT and SVN, but do I really want to remember obscure commands and type them in? No. Working this way does not expose me to any greater security risk. However, I will grant that I probably am not as fast as someone that uses these tools. But I have the peace of mind of the map that a GUI affords me.

In terms of security, I have launched about a dozen Drupal 6 sites and have never been hacked. (Knock on wood.) I'm not so sure that hackers go through the trouble to research what CMS a site is using. My logs show me that I get a constant barrage of anonymous users throwing errors that would be more appropriate to trying to hack an ASP site or a Flash blog or Wordpress, Here are some:

article2/0,4364,1359643,00.asp OR actions/toogleSound OR pages/NAIL媛 OR do/feature

So I REALLY don't believe mentioning Drupal is a magnet for hackers any more than supporting JavaScript or letting the world see that you use php.

One final thing. Many of those security advisory warnings would only effect a site under very specific circumstances. If you are careful about what rights you give users, these alerts may not effect you at all.

_{A list of some of the Drupal sites I have designed and/or developed can be viewed at motioncity.com}