I think I read in another post that it's not a bug really, it's just that the warning message is wrong. If you want to create a chunk of content that stays the same everywhere you put it, you need to code a 'Global Area' into a file in your theme such as a page type file or the header.php or footer.php. When you do that a new Global Area entry will magically appear in the Stacks list where you can build a stack that is truly global.

Here's what I have in my theme in the 'my_theme/elements/header.php' file:



This creates a Global Area in the Stacks called 'header-area' where I have added my auto-nav.

My understanding is that global areas will update the contents of all blocks in the area over the whole site and that every page will have the same set of blocks in the global area. I thought that the purpose of being able to select individual blocks from a stack was so that you could update these in one place, a bit like the old scrapbook.
In my case I have have made a stack containing 6 content blocks of which a combination of 3 would be used on various pages but be updated from the stack if changes to the content is required. I was sure I read about this in a post regarding stacks.

Well bust my britches. I could have sworn I read somewhere in these forums that Stacks had an issue with 'globalarity' but I just tested it and I can confirm 2 things. First, I was dead wrong about stacks. Changes to the parent stack do propagate to the children and second, I can also confirm your issue that a single block pulled from the stack does not reflect changes made to it's parent stack.

UPDATE:

I found the discussion I was thinking about and it actually describes this very issue. In this post, Andrew never answers this specific question.

http://www.concrete5.org/community/forums/customizing_c5/what-happe...

My stacks aren't updating across my site. Granted, I only use one block at a time instead of using the whole stack. And that's the first reason I think this design change was a step backward. But even where I have stacks that contain only one block, and I should be inserting the entire stack when I paste it in, it doesn't update the changes across the site.

So, near as I can tell, the only way to have blocks that will update site-wide is to use multi-block stacks? Or in the case of the above comment, rewrite the code? Is anyone else blown away that the entire genius of websites way back when they were first invented was the fact that we could update a block site-wide from one single location? Did Concrete5 just go three decades back in time?

Now, I have to literally go into hundreds of web pages to update the blocks individually. Unless I'm wrong and anyone else has come up with a better solution. If so, I'd love to find out.

Clear cache?

Make sure stack changes are approved as well as page changes?

The Site is under developement and the cache is off.
I have cleared the cache anyway. I went to the stack and changed the content of a block and approved the changes. I have checked the stack versions and the latest version is approved. The changes made to the block contents are not displaying on the relevent page. I have refreshed the page. If I put the page in edit mode and select the block to edit it is saying that it was copied from etc. as per the image on my first post. I will try this on one of my other sites to see if it is only specific to this site.


Colin
Edit
I have tried this on another site and the stack is not updating blocks that are not inserted as the entire stack

Okay, so after reading posts from the other thread, it looks like C5 is aware of the bug and they're going to fix it so all stack blocks update universally when edited. I wonder when they'll do it, or if they have and I just missed it.

What version is your site?

5.6.0.1 - and it's a newer site using a more recent first install (from Simple Scripts, not a direct install from C5). I've got an older site running the same version and they're nothing alike. But I've got no problem with the one that's been upgraded 5 times over 2 years. It's the newer one that doesn't work right.

I have just tested the stack not updating blocks when an individual block from a stack is inserted on page in version 5.6.1.2.
I can confirm that this has not been fixed in this version. As I am aware of the problem, I don't use this feature and stick to single block stacks, which I can confirm do update or defaults in page types to obtain global updates of blocks.
Has this ever been reported as a bug? It would be a great time saver if it worked as planned.
I was fortunate that I tested this feature at the start of building a rather large site that would relied heavily on the the individual blocks updating site wide.

Colin

Bug reported:

http://www.concrete5.org/developers/bugs/5-6-1-2/individual-blocks-...

This issue still exists in version 5.7.3.1 :(
I'll post a new bug ticket

Confirmed: I can see the same thing
Version: 5.6.1.2

Is this still an issue 2 years later?

:~( I just discovered this bug after creating several Stack "collections" (buttons, categories, pull-quotes) then adding a selection to a page only to find out they are actually separate instances of the content blocks so don't get updated when I either update them in the page OR via the Stacks interface... *cry*

Now I need to re-create individual Stacks for each of those Stack items and re-insert them into every page of my site where they are in use... *cry more, I am so tired already*

I miss my Global Scrapbooks functionality :~(~~ I loved having my Scrapbook collections and then pulling out the item needed and adding it to the page, and then being able to update that item from any page in the site that used it.

Why does using individual Stack elements currently create separate instances? Who wants that functionality?? Just use the clipboard if you are doing copy and paste content blocks... I thought Stacks were for creating re-usable content that had a single source for editing.