There is another alternative to answer this question ... which doesn't require the PHP filter to be enabled (which you should try to avoid whenever possible) ... Just use the Rules block visibility module. Here is a quote from its project page:
The Rules block visibility module allows Rules components to be used to control block visibility. This provides Drupal administrators and developers extreme flexibility in controlling when blocks should be displayed on their websites, in addition to the default visibility options provided by Drupal.
The general idea is that if you can do it with Rules, you can use it to control block visibility, so the possibilities are limitless.
Need to show a block only for users registered more than a month ago?
Perhaps you have a block that must be shown only between 8am-5pm on weekdays?
What about displaying or hiding a block based on current weather conditions?
All of this can be done by using Rules block visibility.
With that, and as per the "if you can do it with Rules, you can use it to control block visibility" above, you've reduced your question to making Rules "check the path of the current page" (so that the block is only shown on your pages with a path that starts with "about-us/
", but not on those pages that have a path like "about-us/*/*
").
For an illustration of how to use this module, refer to my answer to "How to stop a Views block from displaying to admins, such as user/1?". It includes a Rules Component (in Rules export format), which you should replace by this variation of it to make it match your specific question):
{ "rules_block_visibility_show_on_selected_profile_pages" : {
"LABEL" : "Show block on selected profile pages",
"PLUGIN" : "rule",
"OWNER" : "rules",
"REQUIRES" : [ "rules" ],
"USES VARIABLES" : {
"module" : { "label" : "Module", "type" : "text" },
"delta" : { "label" : "Delta", "type" : "text" },
"result" : { "label" : "Result", "type" : "boolean", "parameter" : false }
},
"IF" : [
{ "AND" : [
{ "text_matches" : {
"text" : [ "site:current-page:path" ],
"match" : "about-us\/",
"operation" : "starts"
}
},
{ "NOT text_matches" : {
"text" : [ "site:current-page:path" ],
"match" : "about-us(\/[a-z]*)?(\/)?$/",
"operation" : "regex"
}
}
]
}
],
"DO" : [ { "data_set" : { "data" : [ "result" ], "value" : "1" } } ],
"PROVIDES VARIABLES" : [ "result" ]
}
}
Note: the 2nd Rules Condition in the above Rules Component (with the regular expression in it) may need further refinements to perfectly fit your case. I.e. the "about-us(\/[a-z]*)?(\/)?$/
" part of it (though I think it's pretty close to what your question is about).