These are chat archives for reactioncommerce/reaction

19th
Feb 2016
Aaron Judd
@aaronjudd
Feb 19 2016 00:04 UTC
hmm. because the subscription is initialized in main.js -> unless Shops is being subscribed somewhere else as well..
Spencer Norman
@spencern
Feb 19 2016 00:05 UTC
What I’m seeing is that my packages' code that waits on the subscription is firing before the main.js code
Aaron Judd
@aaronjudd
Feb 19 2016 00:06 UTC
in reaction-layouts, can you change: const subscription = Meteor.subscribe("Shops”);
to const subscription = ReactionCore.Subscriptions.Shops;
and see if that caused the timing..
Spencer Norman
@spencern
Feb 19 2016 00:09 UTC
Doesn’t appear to affect it
Aaron Judd
@aaronjudd
Feb 19 2016 00:10 UTC
ok, well I guess I’ll see if I can replicate somehow.. I’d say just use the shop name from shops for now..
Spencer Norman
@spencern
Feb 19 2016 00:11 UTC
Sure. I’ll see if I can create a reproduction repo too
Aaron Judd
@aaronjudd
Feb 19 2016 00:11 UTC
:thumbsup:
Gabriel Fernandes Lopes Guaitolini
@fuyangli
Feb 19 2016 01:33 UTC
heya <3
Brent Hoover
@zenweasel
Feb 19 2016 02:20 UTC
@fuyangli Hello!
newsiberian
@newsiberian
Feb 19 2016 18:16 UTC
@mikemurray , hi, package enable button doesn't work in dashboard. Simplest fix - update this lines
- const self = this;
+ const self = this.package;
    event.preventDefault();
-    return ReactionCore.Collections.Packages.update(template.data.packageId, {
+    return ReactionCore.Collections.Packages.update(self.packageId, {