Stacks vs Old Scrapbook features2 users found helpful
I work with stacks of the new version 5.5 but I think there are some features missing compared to the old scrapbook.
The features missing are :
1/ Define if stack block (added in a page) is an alias (entire stack) or if blocks in the stack are new instance on the page. ( without using clipboard because we need to go stacks > copy to clipboard a block > go back to page > paste from clipboard ( then sometimes > delete from clipboard) )
2/ Define to display entire stack or just one block in this stack.
3/ Possiblity to rename stacks & blocks in these stacks.
Another question :
There is a way to clear clipboard whitout click on trash for each items ?
Thanks in advance
I get the reason, I understand the logic of the Stack vs. Scrapbook. I just thing the simple little things I could do with a Scrapbook block that I can't with a Stack block. (mentioned by OP)
I can also propose :
> Add ability to make sets of Stacks for organization.
2. Yeah stacks really aren't set up to do this at the moment.
3. 5.5.1 reintroduced the ability to name a block (using the custom template menu on the block itself.)
2. This is HUGE! That's what made scrapbooks great - kept all reusable block is a scrapbook, picked whichever I needed. Now I have to make a new Stack for every block - so it's basically all 1-block "stacks". Not much of a stack now, is it?
Pasting an entire scrapbook was easily possible with the FREE scrapbook display block from the marketplace.
IDEALLY when placing a scrapbook, a scree should come up showing the blocks with checkboxes next to each to select which to place. But anyway, stacks seems to have taken a HUGE step back in this regard.
The BIGGEST BEEF though is that you would introduce this watered down version of scrapbook, claim to have kept scrapbook for legacy but REMOVED THE OPTION TO ADD FROM SCRAPBOOK! That's like saying - "We're replacing cars with tricycles, but you can still keep your car!" I sign up for the tricycle, only to find out that, oh, you're taking the keys.
2. What if we made "Add Stack," when you clicked on it, open a new window with all the blocks in the stack, along with a button at the top that said "Add Entire Stack." Adding an individual block from the stack would basically be akin to going to the stack in the dashboard, adding it to your clipboard, pasting it from the clipboard into your site. Add Entire stack would work the way it does today. That gets back the ability to add individual blocks from a stack, but doesn't backtrack on the reduced complexity (since the user is already in the mode of "Adding from a stack.")
Anyway, it seems like the issue you are having is with semantics, not functionality. I agree, the names could have been better-chosen, and some simple tooltips would have helped - but the functionality was there. It seems that to clear up confusion you just eliminated features.
2. The clipboard seems needlessly laborious...
I am on a page an I want to drop 3 blocks from the stacks. Most intuitive way from user POV is:
A. Click area -> Add from Stack -> Choose Stack
B. Stack contents is displayed, with checkbox next to each item (all pre-checked, if you like)
C. I uncheck the ones I don't need (or I use the super-handy 'uncheck all' at the top and check the 3 I need) - click Add.
If you want to add linking vs. embedding option to the above workflow, just add a per-checked checkbox to the pop-up that says "update these blocks when the stack is updated".
I can't imagine anything being simpler than that - and it seems to cover all possibilities?
In general, I would suggest having an additional tab in the "Add stack" screen for ADVANCED options, where you could have additional features, and add more over time(ex: checkbox to display blocks in random order - which would be great for a variable sidebar on a page).
MOST IMPORTANTLY however, I would just like to reiterate my frustration with the deceptive way in which you deprecated Scrapbook. To claim that you are keeping a feature for legacy, just to have the user find out that, yes, TECHNICALLY you did not lie, but the feature has been rendered useless -- that's not a good user experience, and completely unnecessary. Would have been much more sincere to just keep the 'add from scrapbook' functionality in place (with 'legacy' in parentheses) for at least a few version until there were no more issues with stacks.
Now I am stuck, Sisyphus-like, creating 'stacks' containing one block, KNOWING that I will be undoing all this work once the ability to add individual blocks from a stack comes in.
Thanks for taking the time to read and reply. Good to see senior members of C5 actively addressing issues in the community.
When will you add scrapbook or the functionality of it back in? When is the new update coming out?
learn to love stacks, they'll love you back more.
Lots of comments out here about this, I hope you'll listen and give us a migration path.
1. Maybe continue to give us Scrapbook access, Add from Scrapbook in the dialogues in addition to add from Stacks.
2. Give me some way to put a block on a page into a stack. This whole new clipboard concept doesn't seem to work, because I can't go to a stack and add from clipboard.
Help! We want to use 5.5 on all our sites!
And we really want to update to 5.5 because 5.5 is wonderful.
Stating the obvious: stacks are great! It's just going from scrapbooks to stacks that is sort of a pain in the ***.
Scrapbooks have very usefull but a little complex in terms of organisation, that's right.
Stacks added the ability to insert entire set of blocks in a page and simplify the semantic, but simplifying the semantic this has reduce the features.
So I think we need to combine the both.
1/ No global/personnal scrapbook but only one semantic word : Stacks.
2/ We need to add stacks and put them into "Sets" for organisation, as FileSets.
3/ We need to have the ability ti rename a stack in "Stacks" section, without going in sitemap > check page system" > ...
4/ In front-end, when adding blockType "Stack", we need to have the ability to define if the stack instance is the original instance or if it's a copy. Why ? Because if we want a copy, we need to go in "Stacks" section in dashboard > click on stack > click block > copy to clipboard > come back to website > go edit mode > paste from clipboard. Too many clicks & path too long!
5/ Clipboard can still remain in the core for blocks which are not in a stack (for a faster copy/paste of a block between 2 pages)
6/ Clipboard must have ability to be cleared with only one click.
I just would come back on point 4/ for a more accurate explanation.
Actually, I'm on a WebApp using C5 Power for my company.
This application will generate bids from predefined content.
So, I create a stack for each content.
In front-end, I create a new bid, add from stack, for example "Website development" with his price and description.
OK, but when I want to modify the description for a particular client, I can't without copy/paste from clipboard and for that, I need to do every time the same path to copy/paste...
Sitemap > Options > Show System Pages > Stacks > Properties is obtuse, but it's better than remaking it from scratch.
I find things take longer now. I cannot figure out how to make a stack, let alone use one, nor any detailed instructions about them. What we need is a way to seamlessly convert all our scrapbooks into stacks by pressing buttons. I will be beggared if I am going to re-create every scrapbook entry from scratch just so I can have it as a stack.
To me, this is a bug mistake - HUGE. You are behaving like Microsoft do. Give us all something we like, can understand, which makes sense especially to the more dimwitted of us. Let is all get used to using it, then, in an upgrade, change everything.
I have a number of sites with C5 - I have converted only one so far to the latest version and it is the only site I am going to convert for now. The others are much easier to edit left as they are.
Sorry, but 126.96.36.199 is not really a forward step.