Open acamarata opened 9 years ago
I am also interested in this.
It is pretty hacky, but for now you can do this:
accountsUIBootstrap3.map('en', {
loginButtonsLoggedOutDropdown: {
signIn: "Something",
up: "else"
}
})
That's not too bad actually if there are more priority things to focus on but I didn't find any of that documented so didn't know about it.
On Mon, Jul 13, 2015 at 7:11 PM, Ian Martorell notifications@github.com wrote:
It is pretty hacky, but for now you can do this:
accountsUIBootstrap3.map('en', { loginButtonsLoggedOutDropdown: { signIn: "Something", up: "else" } })
— Reply to this email directly or view it on GitHub https://github.com/ianmartorell/meteor-accounts-ui-bootstrap-3/issues/144#issuecomment-120905756 .
It would be great if we could get rid of the forward slash as well.
That was the main thing I saw is customzing the whole In or Out without a forced slash
On Mon, Aug 17, 2015 at 4:03 PM, Milan Mitka notifications@github.com wrote:
It would be great if we could get rid of the forward slash as well.
— Reply to this email directly or view it on GitHub https://github.com/ianmartorell/meteor-accounts-ui-bootstrap-3/issues/144#issuecomment-131736972 .
Agree that making the divider (slash) on the signin button configurable so one can remove it if needed. Some may not want a "join" or "sign up" feature, like for an admin site. Where in the documentation is the list of all configurable fields?
Well, if the reason for wanting to customize the label is to hide the "Signup" part, you can just set forbidClientAccountCreation to false with Accounts.config and all the signup-related parts of the UI will be hidden.
We are using a different process entirely for signup, and want client-side account creation, but not through accounts-ui. So FWIW, in our case forbidClientAccountCreation is not a solution- we still want Accounts.createUser() to work.
Just a quick follow up, Ian's advice worked of course, but must set forbidClientAccountCreation to true and Accounts.config must go in both client and server.
Yes because of the code stating:
{{#unless forbidClientAccountCreation}} / {{i18n 'loginButtonsLoggedOutDropdown.up'}}{{/unless}}
But what if we didn't want to disable account creation?
On Fri, Jan 29, 2016 at 5:40 PM, neal-eiger notifications@github.com wrote:
Just a quick follow up, Ian's advice worked of course, but must set forbidClientAccountCreation to _true _and Accounts.config must go in _both _client and server, takes a few weeks to get the meteor basics.
— Reply to this email directly or view it on GitHub https://github.com/ianmartorell/meteor-accounts-ui-bootstrap-3/issues/144#issuecomment-176687586 .
Is there a simple non-hack way to edit this or can this be added with a template over-ride (like we do for adding drop down items) or a Accounts.ui.config() option?