I noticed that depending on how you set up pathauto, it has the potential to break settings for what blocks are displayed on what nodes. For example, on the site that I'm setting up, we wanted URLs to the individual blogs to be something like example.com/username, however, with urls like that I can't exclude certain blocks from being displayed on the blogs without using php.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

What is the bug in the software? How should the software behave differently?

So far all that you're saying is that if you shoot yourself in the foot then a gun lets you shoot yourself in the foot... :)

nikkiana’s picture

nikkiana commented

Well, I suppose my thoughts led me to believe that whether a block displayed or not was dependant on what the system url was, not what the pathauto url was...

Maybe some way to either choose whether to display is based on what the system URL is or what the pathauto URL is?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

That would be a bug against core, but really I think that you can achieve what you desire using pathauto and just fixing your block visibility settings.

E.g. instead of example.com/username do example.com/users/[user] and then set the block visibility to show up on /users/*

Here is a typical way of describing the bug you are reporting:

Steps to repeat:
1. create a block and in the block visibility settings have it show on node/1
2. using the path module (not even pathauto) change 'node/1' to 'somethingelse'
3. visit 'somethingelse' in your browser
Expected results:
Block shows on 'somethingelse' since something else maps to node/1
Actual results:
Block is not shown

And that would be a bug against the block module or against path in core. If you feel that should be addressed, please reassign this to the Drupal core block module

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Depending On How You Set Up Pathauto, It can break how Blocks are displayed » Option to display blocks dependent on system path or path alias
Project: Pathauto » Drupal core
Version: 4.7.x-1.x-dev » 4.7.2
Component: Code » block.module

Reassigning and changing title

sja1’s picture

sja1 commented

+1 from me on this one. I just discovered this same problem today, albeit in 4.6. The above workaround (setting alluser pages to /user/username instead of /username) is just that... a workaround. Whether its a bug or a feature request, I'll let someone else decide. Regardless, I think it should be changed so that you do not lose flexibility on block display when using path or pathauto.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (duplicate)

The issue http://drupal.org/node/68187 is for the same issue and has a patch attached so I'm marking 69346 a duplicate of that issue.