Home/ Questions/Q 8965097
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T16:44:22+00:00

I have started a meteor application using the accounts packages for facebook, twitter, github

  • 0

I have started a meteor application using the accounts packages for facebook, twitter, github and auth accounts. For UI, I am using the bootstrap package. Whenevee I load my site projectx.meteor.com, the login links take some time

I have everything static on the HTML page, except for the link to login:

client/x.html:

<div class="masthead">
  <ul class="nav nav-pills pull-right">
    <li class="active"><a href="#">Home</a></li>
    <li><a href="#">About</a></li>
    <li><a href="#">Contact</a></li>
    <li><a href="#">{{loginButtons}}</a></li>
  </ul>
</div>

There is no JS on the client side and I have called the startup method on the server.
Server/startup.js:

Meteor.startup(function () {

});

Also, when I visit the above URL from IE 9 on my Windows Phone 7.5, it doesn’t show the login link at all.

Update: After the comment below, I modified my code to remove packages and additional HTML. The packages now included are:

  • preserve-inputs
  • accounts-ui
  • accounts-password
  • accounts-facebook
  • accounts-twitter
  • accounts-github

I have removed bootstrap and the only thing on my template now is {{loginButtons}}, It still loads the login link after a delay. Is this the default behavior of the accounts package ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The reason why the buttons take so long to load is because Meteor has to ask the server-side for the necessary configuration information (located in a collection in your Mongo instance) before it can render the login buttons for each of the external services you want to use. I think the best solution (and the solution I use) is to simply build the buttons client-side if you want faster results or tweak the login buttons template to allow for data ported in from the client-side using a JSON object with all the OAuth keys it needs.

    • 0