> if I remove the readOnly or change it to false then the
> backstage is no longer hidden
That's because of the startup order; plugins are loaded before the
backstage status is initialized.
Here's a small plugin that will check at the right time:
---
//{{{
// hijack restart
var rest
I am still looking for a fix to my problem. Is there something that I
am missing. I have tried using the [[ConfigTweaks]] idea that was
presented but I can not get it to work. As I said in my last post,
the only way that I am able to get the backstage to be hidden like I
need it to is by using
I reloaded the document after each time I entered a new username. I
am still able to see the Backstage. I also tried searching for
backstage and the only thing that shows up is the [[Config Tweaks]].
I tried loading your fix into an empty copy and was not able to get it
to work that way either
> I tried what you have written but I am able to still see the Backstage
> area regardless of the username that I enter. If it would matter,
> this is not being used on the web but from a file location.
The backstage is initialized when the document is loaded into the
browser. Make sure that yo
Thanks for your quick reply,
I tried what you have written but I am able to still see the Backstage
area regardless of the username that I enter. If it would matter,
this is not being used on the web but from a file location.
--~--~-~--~~~---~--~~
You received thi
> I am looking for a way to hide the Backstage area upon opening unless
> a specific username is used. Everything else should function as is.
Create a tiddler (e.g., [[ConfigTweaks]]), tagged with 'systemConfig',
containing this line of javascript:
-
window.showBackstage=config.options.t
6 matches
Mail list logo