Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have a few blocks on my site showing "top members", "new members" and "top groups". The "more" link is pointing to the matching page display.
The problem is that the link appends an extra "/42" at the end.
For example the "top members" page URL is "members/top" and the "more" link in the block will be "/members/top/42".
The links still work but it will generate a "duplicate content" problem with the search engines.
Any idea what's causing that?
Comments
Comment #1
dawehnerIn views3 there is a feature to allow to set any kind of url you need. This probably will fix your issue.
But really duplicate content is more or less a joke as you can add /foo under each path of your system. Just an example
http://drupal.org/node/1347640/neutrinojoke will still render this issue. This is really 100% a design of drupal. If you don't want to be able to access the page just set up and global: null argument which invalids if the empty is not null.
Comment #3
Ludo.RI have a block that takes nid as argument from URL (to exclude the current news).
The problem is that the more link uses this argument.
So it links to 'news/123' instead of 'news'.
How can we avoid this?
Comment #4
mototribe CreditAttribution: mototribe commentedI guess the workaround is to not use the "more link" setting in the pager and add a "global text" area in the footer with a static HTML link.
Comment #5
Ludo.RYes, I will try this or put it directly in .tpl file.
Thanks!
Comment #6
dawehnerAs wrote above you can now set a custom url for the readmore link.
Comment #7
Ludo.ROk, but is this an expected behaviour?
Comment #9
tbenice CreditAttribution: tbenice commentedHi, Just noticed this and it is definitely a bug. Using the custom url is a workaround, but not a fix. If the more link is set to link to a page display then it needs to set the page display url of the chosen display. Bug still exists in 3.3, changing the version.
Comment #10
anniegreens CreditAttribution: anniegreens commentedAgreed that this seems to be a bug. The Custom URL option does not resolve the issue either, as the query (or argument) is still appended to the URL. In my case it does not affect the display of the page because the exposed filter ID is different for the block and the page.
Updating to current version.