INCOMPATIBLE WITH METEOR 0.9.0 OR LATER about core HOT 18 CLOSED

Hi @CMToups!
I still haven't had time to have a look to the new packaging system, but obviously I'll have to stick with it!
Since it seems you need it, It may be that I'll try to fix all accounts-templates-* today.

Thanks for pointing out this!

from core.

It turns out that the problem is just about how dependencies are specified.
Actually the automatic migration failed because at the moment the reference to accounts-t9n is pointing directly to the github repository instead of a version released on atmosphere.

This means that also the migration of accounts-t9n should be fixed before proceeding.
At the moment I'm thinking whether to fork the project to be ready right now or simply waiting a few days to have things settled down a bit more.
The main problem is figure out how to maintain both versions (for the new package system as well as for the old one) without breaking none of the two. Ending up with two different repositories doesn't seem to be the better solution...

from core.

@splendido thank you for your quick reply. I expect these are questions most of the package maintainers are asking right now. From my end I have weeks of runway before I need a stable login so please avoid a fork.

When meteor 0.9 is out then maintaining both versions may become an issue. That said the meteor google talks have lots of discussion on this issue. There was even talk of using meteorite v2 for things like this.

Please just keep 0.9 in mind over the next week or so, thanks!

from core.

Looks like the latest release works with meteor 0.9.0. Sign in / Sign up works like a charm, thanks!

from core.

Hi there,
good to hear this!

...actually I've discovered some problems, but they might not show up depending on the settings you use.
What more, we'll have to wait for a new release of accounts-t9n to get all info and error messages.

Please be patient! We'll get there! ;-)

from core.

Yeah, I was just seeing some issues here and there. Namely:

AccountsTemplates.configureRoute 'resetPwd'
AccountsTemplates.configureRoute 'enrollAccount',
  layoutTemplate: 'emptyLayout'

Neither routes render and layoutTempate is ignored in favor of my top level layout. But the basic functionality works and I can wait on the rest ^_^

from core.

That's what I'm into at the moment...
I think they'll be shown if you enable the password change flag.
Will be fixex soon!
...as for the layout, I'll try to mame so e tests.

Thanks for the feedback!

from core.

@splendido I really like what you're doing here. I am still in development and have just done some minimal integration with accounts-ui and was frustrated with the lack of ability to customize. I've looked at some of the alternatives, but didn't really like what I was seeing. I just came across your project and it looks like something done very well. On the 0.9.x support, I would hope that at some point, most projects out there will migrate to 0.9 and then ultimately 1.0. Perhaps some will continue to need support for 0.8.x, but I suspect that the numbers would be small. My advice would be to go strong toward 0.9.x and become the best accounts package. Thanks for your efforts.

from core.

Hi @bobmonsour!
I'm so pleased to hear this, you made my day :-)

At the moment my idea is to keep updating the package both for .8.3 and .9.0; at least as long as the few dependencies will permit it, without the need to fork the code.

As you may have noticed there's a big reorganization of the code in progress, and a few optimizations are also on the list...
Hopefully a 1.0.0 version is getting closer and closer.

The interest abiut this project seems good (as you're also confirming) and this is enough for me to try my best to bring it to a stable and complete status, even if my spare time is really too few to get things done as I would wish...

...so please keep posting about any problems, ideas, criticisms and so on.
PR are also always welcome.

Thanks again,
Keep in touch!

from core.

@splendido depending on how much is left do you want to make a 1.0 milestone? I am kinda busy with three active meteor apps but all of them will use this package. If I know what you need I might be able to add a PR or two.

from core.

@splendido Thanks for your quick reply. I'll definitely let you know if I run into problems integrating accounts-templates-bootstrap (my intended integration). I very much appreciate what appears to be very good documentation on how to use it. That was my biggest problem with some of the other alternatives. They seemed to require a lot of guessing and assumed a lot of knowledge. I'm relatively new to Meteor and am starting to get the hang of it (having a lot of fun.) The accounts piece is very important to me as I want to make it feel seamless with the app. I've just completed integrating both Intercom and Mixpanel and have to finish getting the accounts setup working as I want it to.

I see that you are in Italy. Your english is excellent (assuming you're a native Italian). I recently began taking an Italian language course to better communicate when my wife and I travel again there. She has family in the Veneto.

Thanks again for your work.

from core.

Lets drop a line in case you travel through Parma! ;-)

from core.

Everythings seems fine, also with Meteor 0.9.0.1.
I'm closing this here for now.
Let me know about any problem!

from core.

Do I understand that the package should work now with 0.9? Because I can't get it to work...
I have everything set up as I had in 0.8... I depend on it through meteor, not through meteorite.

from core.

Hi!
I'm aware it does' n work with preview releases, but should work as is with 0.9.
What's the error you're getting?

from core.

I'm sure this boilerplate works:https://github.com/splendido/meteor-at-boilerplates?files=1

from core.

I'm trying to adapt everything like the boilerplate, but I still get this error:

Uncaught ReferenceError: AccountsTemplates is not defined at_config.js:4(anonymous function) at_config.js:4(anonymous function) bangama-frontend.js?bb6d92597ff978bd60a07d184617602c6a09233c:89(anonymous function) main.js:173

If I run the boilerplate local, it all works... so i guess I'm doing smth wrong...

EDIT: I think I solved it. Problem was I did the AccountsTemplates.init(); not on both server and client.
Thanks for the response...

from core.

Good!
Thanks

from core.