By andre75 on

After upgrading from 4.6 to 4.7 i noticed that all the Home links now point to example.com/node instead of example.com.
This page has a pagerank of 0 and looks exactly the same as the hp (example.com) to google (duplicate content is a problem with google and can lead to a drop in PR). While the actual hp lost a lot of (internal links).

I went to settings / General and tried to change the Front page from "node" to "" or "/", but now I am getting a page not found error.
I have searched drupal.org and not found a solution. Even worse, drupal.org behaves this way itself
(just click on any breadcrumb home link and you will see that you end up here drupal.org/node which is an exact replica of drupal.org). Google isn't going to appreciate this and I would really love to find a way to change this on my site.

Andre
http://www.opentravelinfo.com
http://www.aguntherphotography.com

⋅ Categories: Drupal 4.7.x

Comments

andre75’s picture

andre75 commented

Noone is bothered by this? Is it only me who thinks that duplicate content is a problem?

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

sepeck’s picture

sepeck commented

It's had this behavior for quite some time across several versions. Drupal.org has this behavior and it hasn't affected anything. Your home page is set to /node by default and in admin >> settings so that's where you go. It's not duplicate content.

There are a lot of myths about Google page ranks and such.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

andre75’s picture

andre75 commented

Thanks for your answer. However I have to strongly disagree with you. My photo website does not show this, and after upgrading my travel website did. However /node was pr0, which means that until now, google hasn't seen it (the home page is pr5). I don't want to change my site structure and I dont want incoming links to point to / while internal links point to /node. This splits up the link count to the front page and is generally not a good thing.
What I am asking for goes along the lines that suggest that you use only www.domain.com or domain.com and forward one to the other (even drupal.org does this). The same reasoning should apply to / and /node
Either way, would you happen to know a way to change this behavior? I would really love to put the linking structure exactly the way it used to be. Right now I am forwarding it with a 301, but I don't consider this the perfect solution.

Thanks again for taking notice.

Andre

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

venkat-rk’s picture

venkat-rk commented

I am not sure if this is a typical problem in 4.7. I have never noticed any of my 4.7 sites, whether upgraded from 4.6, installed in a subdirectory or installed in a subdomain pointing to example.com/node on the Home link in the breadcrumb.

I think this might be a theme related problem. Did you make any changes to page.tpl.php? I noticed this with the Ocadia theme, for instance. I added bits of code from bluemarine to make it provide breadcrumbs and primary links and thereafter, the home link in the breadcrumb would always point to www.example.com/node

andre75’s picture

andre75 commented

Do you have any pointers how to fix this?
I am using the sands css theme:
http://drupal.org/node/57629

In the theme i can only see these two occurances of breadcrumbs.

in template.php

function sands_css_breadcrumb($breadcrumb)
{
  return implode(' » ', $breadcrumb);
}

and in page.tpl.php

    <?php if ($breadcrumb) print "<div class=\"breadcrumb\">$breadcrumb &raquo; $title</div>";

?>

Quite frankly I wouldn't know what to change here. Do you still remember what you did?

There is a whole bunch of breadcrumb stuff in common.inc, menu.inc, theme.inc, blog.module, book.module, comment.module, forum.module, node.module, taxonomy.module, user.module. But that would have nothing to do with the theme.

Thanks for the hint.

Andre

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

sepeck’s picture

sepeck commented

I meant the link to /node. My bad on the home breadcrumb. Try changing to a default theme and see if the issue still persists. My site's breadcrumb has always had this behavior in 4.7.2 and 4.7.3.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

andre75’s picture

andre75 commented

Good point.
I tried bluemarine, but it showed the same kind of behavior. I almost think that its default behavior in Drupal. Ramdak might just have discovered a theme that overwrote this. Could you help me out to find the right code Ramdak?

Since Drupal.org itself behaves this way, I do think that its default.

Andre

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

venkat-rk’s picture

venkat-rk commented

This is interesting- I AM seeing the same behaviour (www.example.com/node) on 4.7.3 with default bluemarine where the drupal install is at the root of the domain. I am NOT seeing it on a 4.7.2 site installed in a subdomain irrespective of the theme I use.

I also have a couple of upgraded sites (all 4.7.2) installed in subdirectories and a whole bunch of test sites running 4.7.2 where the install is in a subdomain and don't see this behaviour.

This seems to rule out theme issues. Something seems to have changed between 4.7.2 and 4.7.3 that's causing this. Yuck, this is one more thing to worry about now...

andre75’s picture

andre75 commented

Thanks for the pointers. I will do some diff on comparing the 4.7.2 to 4.7.3 to see what might cause this.

Sepeck: Do you think it makes sense to submit an issue to the Drupal Core Developers to get this reversed in the next release?
Overall I think it makes a lot more sense not to have everything pointing to /node but / instead for the reasons I outlined above.

Thanks Ramdak!

Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

ericatkins’s picture

ericatkins commented

Submitted a bug report: http://drupal.org/node/78129

andre75’s picture

andre75 commented

I just logged in to do the same, but fortunately I checked this thread first.

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

venkat-rk’s picture

venkat-rk commented

Here's something interesting. In a forum comment I made, I had left out the 'http://' in a link to the CCK filefield project and the link showed up like http://www.drupal.org/node/www.drupal.org/project/filefield

When I added the http, the link showed the correct form of the url. Might this problem we are discussing simply be because of a variable in phptemplate or wherever referencing the base_path without the 'http://'?

I know this is a bit of a wild guess...

Reverend’s picture

Reverend commented

The base_path variable does indeed appear to have a quirk to it. I first noticed this behavior after using the Front_page module. If visitors came to the site via the conventional www.domain.com URL then Front_page worked as intended. If someone came to the site using just domain.com then the breadcrumbs would display a different (and unwanted) link as my home page.

The next time I noticed it was after making some minor (to my mind anyway) changes to a template and discovering some odd results.

It seems that the core makes certain assumptions about the base_path variable for the sake of brevity and consistency, perhaps.

andre75’s picture

andre75 commented

Ramdak:
I noticed the same behavior, but I don't think it has anything to do with this problem. I get drupal.org/www.somesite.com (no node I believe). This seems to be a completely unrelated issue though?

Reverend:
I believe putting this:

RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]

into your .htaccess file may solve that frontpage issue. This should be done anyways, to avoid pagerank spreading between two domains (google treats domain.com and www.domain.com as two different domains).
Alternatively you can also redirect everything to the non-www domain (just as drupal.org does)

Andre

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented

if you want to try out a fix, go here:

http://drupal.org/node/78129

--
Drupal tips, tricks and services
http://devbee.com/ - Effective Drupal

--
Devbee - http://devbee.net/

andre75’s picture

andre75 commented

Thats what I call fast :-)

I will defenitely give it a try.

Andre

-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com

TheWhippinpost’s picture

TheWhippinpost commented

Just to say a big thanks to Harry for saving me, probably, several hours in debug-work... another path problem fixed!

For others running into this problem in 4.7.x, (probably most folk), the fix found at: http://drupal.org/node/78129, works fine.

Mike
------------------------------------------------------------------------------------------
A simple thanks to those that help, a price worth payng for future wealth.