Posted by AstralP on February 7, 2007 at 5:28pm
Jump to:
| Project: | Block Cache |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
The rules from the 'Show block on specific pages' block don't seem to be followed. I have many blocks that are on just on certain pages utilizing the 'view only on the following pages'
Does this not work or am I missing something? Great idea for a module btw.
Comments
#1
how are you adding the page ?
example:
admin < would show on only admin page
admin/* < would show in admin path
both of the above would be needed to show block on admin page and anywhere in the admin path.
#2
I generally have been using just;
blog*
user/add/blog*
This works for the standard modules and covers everything in the paths. It is more work for me & the site to use blog/* because the blog posts go in a category called blogs and the above example covers both paths in one go.
Just had another look and discovered that blockcache does not carry these setting forward from the original block. If they are set on the cached block itself it works. I was under the impression that all setting were carried forward. I thought I'd tested that last night, but obviously not :) It may be worth adding this to the readme file.
thanks again
Andy
#3
#4
Not copying the block specific path details over for the cached version of each block is proving a nightmare. Especially on a site with 50+ blocks and all happen to be page targeted.
I am not sure whether this is considered a feature request or a bug request, as the title of the block is followed, but any other info such as roles and paths do not appear to be followed across for the cached versions.
#5
How can i make it in code???
'pages' => 'public/*\r\naboutus\r\naboutus/*',
t() i used - no results
array - used -no results..
HELP me...
#6
$blocks[2] = array(
'pages' => "public/*\r\naboutus\r\naboutus/*\r\nexpertadvice"
);
I made it.
Sorry for the OFF TOP