Help! Spurious password protection...
Mark Smith
mark at maseurope.net
Sat Mar 8 20:03:04 EST 2008
It was my own fault - I had a custom property called 'password' (not
for locking the stack) - completely forgetting that it's a reserved
word...doh!
Fortunately, the stack was at an early stage, so not much lost.
5523 is still off limits for me...
Thanks,
Mark
On 8 Mar 2008, at 23:15, Richard Gaskin wrote:
> Mark Smith wrote:
>
> > On 8 Mar 2008, at 19:32, Richard Gaskin wrote:
> >> Does this warning about the stack being locked occur in v2.8.1
> >> only? If so, may be related to this item fixed for v2.9:
> >>
> >> <http://quality.runrev.com/qacenter/show_bug.cgi?id=5523>
> >
> > The qa center tells me I'm not authorised to view that bug - I
> hadn't
> > realised there were special, classified bugs!
>
> Weird. When I click the link above it goes straight to my report.
> Maybe once an issue's been closed only the original reporter has
> access? I dunno, but here's the body of that report:
>
> Going from locked stack to unlocked in same window is weird
>
> When going from a password-protected stack to one that
> isn't password-protected in the same window, an error
> is generated when you attempt to edit the second
> stack's script.
>
> Using the attached example files, try this recipe:
>
> 1. Open start_here.mc
> This stack is password-protected (password: "test"),
> but don't unlock it yet.
>
> 2. Click the button in that stack.
> That will cause the second stack to be opened in the same
> window
>
> 3. Try to edit the script of the second stack
>
> Result: you will get an error that the stack is
> password-protected, but you won't be able to edit it
> because the editor's check for passwords (password
> is not empty AND password <> passKey) passes, yet the
> stack is flagged by the engine as locked.
>
> It would appear as though the password protection is
> mistakenly bound to the window, rather than the stack
> object.
>
>
> --- Comment #4 From Mark Waddingham 2007-11-20 01:13:38 ----
>
> Fixed in 2.9.0-dp-2 (Beta 9).
>
>
> All this assumes, of course, that the password property of the
> stack in question is indeed empty. Have you verified that that's
> the case?
>
> --
> Richard Gaskin
> Fourth World Media Corporation
> ___________________________________________________________
> Ambassador at FourthWorld.com http://www.FourthWorld.com
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
More information about the use-livecode
mailing list