If you create a page with an alias of "test", and set a block to show up only on "test", then go to "TeSt", the same page will appear, but the block sees it as a different page and will not appear.

This _might_ have security implications, although I don't see how.

CommentFileSizeAuthor
#5 drupal_block_visibility_case_702010.patch1.31 KBjastraat
#4 drupal_block_visibility_case_702010.patch1.31 KBjastraat

Comments

mr.baileys’s picture

mr.baileys
Primary language Dutch
Location 🇧🇪 (Ghent)
commented
Status: Active » Closed (duplicate)

Duplicate of #368093: Block visibility settings are case sensitive ?

adamfeldman’s picture

adamfeldman commented
Status: Closed (duplicate) » Active

This is not fixed as of 6.19. I have a URL of type "aBcd", which shouldn't be a problem if the entire URL string is being converted to lowercase.

manos_ws’s picture

manos_ws commented

This is not fixed for 6.20 , in the issue #368093: Block visibility settings are case sensitive ? there is a patch on post 47 and they say its committed. I guess its only committed for drupal 7. When I review the code of block.module in 6.20 and the patch code is not there.

Manos
http://websynergy.gr/

jastraat’s picture

jastraat commented
Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new drupal_block_visibility_case_702010.patch1.31 KB

Confirmed this is still a problem with 6.30.

Re-rolled the patch from #368093 and tested the new patch with the latest version of 6.x

It fixes the issue. This does seem to be a bug since paths should be case insensitive. Any chance we could get it applied?

jastraat’s picture

jastraat commented
StatusFileSize
new drupal_block_visibility_case_702010.patch1.31 KB

Removing trailing spaces

mr.baileys’s picture

mr.baileys
Primary language Dutch
Location 🇧🇪 (Ghent)
commented

To be honest, I don't think this will ever make it into D6. For one, committing this to D6 might break existing sites (blocks that were not showing up on some pages because of the bug could suddenly start appearing after this fix. We should be very careful changing existing behavior). In this case it seems wiser to just leave it as is for D6 and mark this as a won't fix issue...

jastraat’s picture

jastraat commented

This was fixed in Drupal 7 however - so it would prepare clients who will eventually be upgrading to the new case-insensitive behavior.

I understand if it doesn't make it in, but it does seem to be a bug and was reported by one of our clients as such.

Status: Needs review » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.