The path is not transformed to lower case (or upper case) when this is selected. "Transform spaces to dashes in URL" works but kills the links from summary items.
Cheers
Alan

CommentFileSizeAuthor
#9 activity-displays.jpg135 KBGeijutsuka
#9 activity-rendered.jpg32.84 KBGeijutsuka
#9 program_sections.txt20.26 KBGeijutsuka
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Active » Postponed (maintainer needs more info)

Can you please tell some more information?

http://drupal.org/node/571990 has some good content how to report a helpful issue, you know everyone wants to have issues fixed, so do you, so more information dramatically helps.

thebeepseal’s picture

thebeepseal CreditAttribution: thebeepseal commented

Thanks Dereine and apologies that I have only just seen your reply. I take your point, so here is more information.

I have a View set up to display Content Fields of a custom content type "Event". I then have a Contextual Filter on the Title - for example, "Rolling Stones Play Aberystwyth". In the MORE section of the Contextual Filter config page I set "Case in Path" to lower case and I check "Transform spaces to dashes in URL".

The Views page path is /individual-events.

Now, I would expect the path in the URL to look like this:

"www.mydomain.com/individual-events/rolling-stones-play-aberystwyth"

But it looks like this:

"www.mydomain.com/individual-events/Rolling-Stones-Play-Aberystwyth" - i.e the case is not transformed in the path.

Strangely, if I set up a link in another page, either of these will work.

I may be misunderstanding how "Cae in Path" is supposed to work - my apologies if that is the case.

Many thanks

thebeepseal’s picture

thebeepseal CreditAttribution: thebeepseal commented
Status: Postponed (maintainer needs more info) » Needs review
thebeepseal’s picture

thebeepseal CreditAttribution: thebeepseal commented
Status: Needs review » Active
dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

I have a View set up to display Content Fields of a custom content type "Event". I then have a Contextual Filter on the Title - for example, "Rolling Stones Play Aberystwyth". In the MORE section of the Contextual Filter config page I set "Case in Path" to lower case and I check "Transform spaces to dashes in URL".
This option below is just used for the summary/glossary functionality, as this is the only place where views arguments output a link. Maybe you mixing up something here.

philsward’s picture

philsward CreditAttribution: philsward commented

I'll agree that this scenario is not working as intended...

I'm in the process of migrating from D6 -> D7. In my sandbox now running a successful migration to D7, I've noticed that the path is not working as intended...

I have a FAQ for "Buyers" and "Sellers" which are both Taxonomy terms in a Vocab: FAQ.

I have a FAQ page with a path set to /faq and a contextual filter set to: (term) Taxonomy term: Name (or rather that's how it was automatically migrated). I have the contextual filter to show a summary so I get:

Buyers
Sellers

Having the "Case in Path" set to lower case, I expect the links from the summary to be:

/faq/buyers
/faq/sellers

However, the links are instead showing:

/faq/Buyers
/faq/Sellers

Looking at my still intact production D6 site running views 3 also, the path structure is all lowercase as expected.

In addition, after running into some weird issue with getting my FAQ to work, I decided to completely rebuild the view which did not help solve the problem. (meaning I don't believe it's a migration issue of data from D6 -> D7)

philsward’s picture

philsward CreditAttribution: philsward commented

I personally wouldn't mind seeing this bumped on account of SEO issues that can crop up from the same page having two different URL variants: (uppercase vs lowercase)

zaen’s picture

zaen CreditAttribution: zaen commented

Look at handlers/views_handler_argument_string.inc, for this function (line 233 on version 7.x-3.3):
function summary_argument($data) {

The next line is this:
$value = $this->case_transform($data->{$this->base_alias}, 'path_case');

Change it to this:
$value = $this->case_transform($data->{$this->base_alias}, $this->options['path_case']);

This appears to already be fixed in the most recent 7.x-3.x under version control.

Geijutsuka’s picture

Geijutsuka CreditAttribution: Geijutsuka commented
FileSize
program_sections.txt20.26 KB
activity-rendered.jpg32.84 KB
activity-displays.jpg135 KB

I have a similar issue—most likely related—regarding the "More link" under the pager settings.

My scenario:
Page view with an attachment (see attached mockup and screenshot) and contextual filters are

  • Content: Has taxonomy term ID (with depth)
  • Content: Has taxonomy term ID depth modifier.

Page shows all nodes of a content type called Activity, and the attachment shows one node of a content type called Gallery. The attachment has a "More link" (located under pager settings). I've set the more link's URL to a custom URL in the "Link display" settings (goes to a different view that lives at galleries/%1).
All-in-all I thought that should do it, but when I clicked on the attachment's more link, it went to a non-lowercase path for %1 (i.e. instead of going to /galleries/aquatics it went to /galleries/Aquatics). It's great that views keeps the capital letter when overriding titles, but keeping the cases seems to have bled over into some path functionality...

I've also attached my exported view. Please let me know if any of this is unclear and I'll do my best to clarify (wish I could help more...).