Lock in partials


(Lisa Sandler) #1

Can someone please explain what “lock” does in partials? Because it sure doesn’t lock anything for me. I still sometimes click on partials and open them when not meaning to, even when they are supposedly locked. A real lock feature would be very welcome.
@isaiah


(Jannis from inStacks Software) #2

What’s your version number of stacks?


(Lisa Sandler) #3

The latest but not beta. 3.2.7b4


(Jannis from inStacks Software) #4

You first have to look the stack, and then create the partial out of it.


(Lisa Sandler) #5

? I have to lock a stack first then create a partial? and then the partial will not be able to open?


(Jannis from inStacks Software) #6

At least in 3.5beta…


(Lisa Sandler) #7

ok. Wish there was a way of grouping and locking but maybe in the future Isaiah will be able to come up with that.


(Isaiah Carew) #8

Can someone please explain what “lock” does in partials?

You would not believe how much sleep I lost in deciding what pushing the lock button should do to a partial. :stuck_out_tongue_closed_eyes:

So… this is a great question!

OK, here goes:

When you lock a partial what you are locking is that instance of the partial. In practice what this means is that you lock out all changes to un-pinned content – and to the settings on that instance itself (like if you added a border around that instance).

So… for many partials (most partials?), where there is no unpinned content at all, locking doesn’t do much. So you hit the nail on the head :hammer:.

In short: you can’t edit a partial without pushing into it. To lock the content in a partial – push into the partial, then lock the stacks inside.

What there currently isn’t: any way of preventing you from pushing into a partial.

Do you think locking a partial should prevent that?

That would prevent stray-clicks from pushing in – and I think that would be a very nice addition. I’m going to put it on the feature request list for 4.0

Isaiah


(Lisa Sandler) #9

@isaiah thank you for the explanation.

I have a hard time with partials because they open so easily and then it makes all my pages have changes to republish. So yes, if I could lock a partial (the total “group”, not necessarily the unpinned content–if I am labeling this correctly–so that I can’t push into it as you said, unless I want to) so that it shouldn’t open, that would be great.

OR, if it opens and I don’t change anything, then close it, would you be able to make it so that it doesn’t show changes?

Does that make sense for the reasoning behind my post?

thanks, Lisa


(Isaiah Carew) #10

So yes, if I could lock a partial so that it shouldn’t open, that would be great

:+1: I’ve added this as a feature request so you can track it and keep me honest. :wink:

https://github.com/yourhead/s3/issues/730

OR, if it opens and I don’t change anything, then close it, would you be able to make it so that it doesn’t show changes?

Ahhh… that one is easy – because it’s already done. :tada: Just download the Stacks 3.5 (or hang tight – I think the release is very soon now). But that was a bug I fixed a few weeks back.

Does that make sense for the reasoning behind my post?

Absolutely.

Also: never doubt your own confusion. you don’t have to apologize for it.
more advanced features naturally have larger learning curves – but it’s my job to keep the curve as small as possible.

IOW: when you’re confused, that’s my bug. always feel free to let me know. i can’t always fix it, but i’ll always try.

Isaiah


(Lisa Sandler) #11

Awesome! Thank you! I always tell the developers, I am a designer, not a programmer, so I think differently. So glad you get it :slight_smile:


(Greg Schneck) #12

@Isaiah - Thank you for all that you do, thank you for your participation here in the forums, and thank you for the time you spend helping and explaining…