Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
block.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 May 2008 at 03:08 UTC
Updated:
7 Jan 2011 at 18:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stevenpatzComment #2
sonobor commentedAgreed. Does inserting "none" do the trick?
Or does that cause some sort of error?
Comment #3
escoles commentedinserting any string which matches no path (e.g. "x") will cause the block to not be displayed. "
<none>" will also work.However, this should not be necessary. This is clearly a bug. The system is behaving in precisely the opposite manner that its settings indicate that it should.
This behavior seems to indicate that what's happening is the field is just never checked if it's empty.
I've just verified that this behavior occurs on both 6.9 and 6.14. I'm updating the version to 6.14, since it's still present.
Comment #4
escoles commentedChanging title to make more descriptive.
Comment #5
mr.baileysMarked #739486: Block visibility as a duplicate. The same issue applies to 7.x-dev, so will need to be fixed there first and then backported.
Comment #6
mr.baileysThis also applies to the PHP visibility setting: if you select "Pages on which this PHP code returns TRUE (experts only) " and leave the text area empty, the block will be shown on all pages. This contradicts the UI text and is confusing...
Comment #7
mr.baileysAdded a test.
Comment #8
casey commentedNeeds a reroll.
Comment #9
jody lynnRerolled to remove bits of the test patch already committed.