deletion of block from page defaults does not clear child pages1 user found helpful
This worked fine.
When I later deleted the block from the defaults however it still shows up on all the child pages - even though the block has now gone from the default. I will need to delete it individually from each page.
Is this normal behaviour? It seems strange to have the feature to add a block to multiple pages - but not to remove it!
Incidentally the page defaults/scrapbook screencast video appears to be broken. It crashes at 1:32 in both IE and Firefox.
You could also use the global scrapbook. Will work some more reliable I guess.
is there some other solution for this?
What I found is you have to set up the child pages again before deleting it from the parent page. Deselect all the pages it and it will be gone.
Doesn't help you now, but it might in the future. If anyone has any more ideas on the original question, I'd love to know myself.
1. Created block on page type.
2. Set up block on child pages.
3. Deleted block on page type.
4. Block is still across all child pages.
Help please? I have over 500 pages with this block now set up on them.
Simply put, you want to delete the block from all pages. It's just two, simple steps. 1. Deselect all child pages. 2. Delete the block from the default template so it is gone for future pages.
The default template page is ONLY used to setup NEW pages when you set them up, according to what it is you want on the default page. It isn't like a Master control page which continues to filter down to other pages, UNLESS you select the Setup on Child Pages check box, which is the reverse concept.
I've actually been using a solution with a lot of success recently that solves a lot of these problems -- I use the free "Global Areas" addon, add that to the page defaults and point it to the home page. Now instead of going to the page defaults to edit the content, you can just edit the home page and it will automatically update on all other pages as well. You can even change the order of the blocks and have that update as well (which is not something that works on Page Defaults). This isn't a perfect solution, because it is only for entire areas of a site, and you couldn't just remove one block on one page and leave all the rest without affecting every other page too. But for 90% of the things I used to do with Page Defaults, I've found this to be a much better solution.
Hope that helps.
> and point it to the home page.
I've not used that block or tried that approach, but if I understand what you're saying, then if your home page layout is unique (which is the case for nearly all the sites I build), then you'd have to pick some "internal" page to use as your "master template". Is that right?